Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fda0a3e84ddad71ffe7e8246df1c47b9647ba56239fe1f4e440b87f497ee7ab1

Tx prefix hash: 82229fbd81d8400fd2cd47b36bc72890843bc2eebab14a6540e78e0ee612bc42
Tx public key: 4d0715cdf71fef3b55deb784f699b8519c1ace9decd92d4e4ea323b46abf228d
Timestamp: 1737390044 Timestamp [UCT]: 2025-01-20 16:20:44 Age [y:d:h:m:s]: 00:149:07:01:36
Block: 1201531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106437 RingCT/type: yes/0
Extra: 014d0715cdf71fef3b55deb784f699b8519c1ace9decd92d4e4ea323b46abf228d02110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b3d718c2483cdb44fe371fd53dc2fdaed2a6e86744b88d8897d40a3daa319b7 0.600000000000 1688184 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": 1201541, "vin": [ { "gen": { "height": 1201531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b3d718c2483cdb44fe371fd53dc2fdaed2a6e86744b88d8897d40a3daa319b7" } } ], "extra": [ 1, 77, 7, 21, 205, 247, 31, 239, 59, 85, 222, 183, 132, 246, 153, 184, 81, 156, 26, 206, 157, 236, 217, 45, 78, 78, 163, 35, 180, 106, 191, 34, 141, 2, 17, 0, 0, 0, 11, 31, 10, 83, 235, 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