Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d77955e2779825bf8e3e8d1fa6b8934625fa6224a756bc6cd791cbb5e30d1041

Tx prefix hash: d5276f93a61dbb1caf3bbb1493df51c44739cbe8d88b9022228dfcc805da48a3
Tx public key: 23094fe3b13d4774bfb70f1966fe1cc1c5e97e37bdc4c06f75327b1865b33b3c
Timestamp: 1715378333 Timestamp [UCT]: 2024-05-10 21:58:53 Age [y:d:h:m:s]: 00:342:07:53:24
Block: 1019256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244684 RingCT/type: yes/0
Extra: 0123094fe3b13d4774bfb70f1966fe1cc1c5e97e37bdc4c06f75327b1865b33b3c02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83374bd790ab31714a2a793ad43054137fb6b8db4a75351e68f0a5c74836acd2 0.600000000000 1483177 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": 1019266, "vin": [ { "gen": { "height": 1019256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83374bd790ab31714a2a793ad43054137fb6b8db4a75351e68f0a5c74836acd2" } } ], "extra": [ 1, 35, 9, 79, 227, 177, 61, 71, 116, 191, 183, 15, 25, 102, 254, 28, 193, 197, 233, 126, 55, 189, 196, 192, 111, 117, 50, 123, 24, 101, 179, 59, 60, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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