Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 0261045ec4c77e5c3c178421d77ed0c462d87355307dcc87cb986d8b728c2873

Tx prefix hash: 3ec1615b038f85740009bf788c8af22553c99a24c2449b952bf3ad8de7da83c3
Tx public key: 46415a3cf5b8a2162ac5ca24a6bbb898d2cc6570eb9d515e1a90a43ac050e3f1
Timestamp: 1721951630 Timestamp [UCT]: 2024-07-25 23:53:50 Age [y:d:h:m:s]: 00:236:19:58:41
Block: 1073730 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169191 RingCT/type: yes/0
Extra: 0146415a3cf5b8a2162ac5ca24a6bbb898d2cc6570eb9d515e1a90a43ac050e3f1021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5071733ba3ce35093966459b79df1ff4dffe8e0d93c4550412b2b8f0eea387f 0.600000000000 1546237 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1073740, "vin": [ { "gen": { "height": 1073730 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5071733ba3ce35093966459b79df1ff4dffe8e0d93c4550412b2b8f0eea387f" } } ], "extra": [ 1, 70, 65, 90, 60, 245, 184, 162, 22, 42, 197, 202, 36, 166, 187, 184, 152, 210, 204, 101, 112, 235, 157, 81, 94, 26, 144, 164, 58, 192, 80, 227, 241, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8