Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a18a0c4ae91a6071581b8b819dd7cb565602a20e8bd824da36f91798e86495e2

Tx prefix hash: f2c7099ec7e0bb405dba22e2d32db33b964dd7dff181d9b42eae7640a5a489a4
Tx public key: 21fc357a8551fe05a69e4697a882dbeabd60a4f67f0ece59708353f1221341d2
Timestamp: 1744267257 Timestamp [UCT]: 2025-04-10 06:40:57 Age [y:d:h:m:s]: 00:034:11:23:58
Block: 1258245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24672 RingCT/type: yes/0
Extra: 0121fc357a8551fe05a69e4697a882dbeabd60a4f67f0ece59708353f1221341d20211000000056c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b801116d3d7035fe1d441aac5f29083ea5bb8b0e2c1c6d5d204c23eccb9a2e1 0.600000000000 1745378 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": 1258255, "vin": [ { "gen": { "height": 1258245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b801116d3d7035fe1d441aac5f29083ea5bb8b0e2c1c6d5d204c23eccb9a2e1" } } ], "extra": [ 1, 33, 252, 53, 122, 133, 81, 254, 5, 166, 158, 70, 151, 168, 130, 219, 234, 189, 96, 164, 246, 127, 14, 206, 89, 112, 131, 83, 241, 34, 19, 65, 210, 2, 17, 0, 0, 0, 5, 108, 152, 170, 61, 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