Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9316647dda925d58e1064784d4473e8a4428ef37b006c6645e0db969b8df28c

Tx prefix hash: acf2dd61a85d6928bf72f27bae719b3883957ac2b93c9a7152dc0415f91b3b12
Tx public key: f14e3e9ab9266af591ea985f882b81ecfd7090761321f31c96c3f7ba92e8f983
Timestamp: 1731455258 Timestamp [UCT]: 2024-11-12 23:47:38 Age [y:d:h:m:s]: 00:216:22:48:54
Block: 1152423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154814 RingCT/type: yes/0
Extra: 01f14e3e9ab9266af591ea985f882b81ecfd7090761321f31c96c3f7ba92e8f9830211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a02210a06ff16f9ca0e05839f1e5d5708d0b0491db1729c706c66d67fe27842e 0.600000000000 1638020 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": 1152433, "vin": [ { "gen": { "height": 1152423 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a02210a06ff16f9ca0e05839f1e5d5708d0b0491db1729c706c66d67fe27842e" } } ], "extra": [ 1, 241, 78, 62, 154, 185, 38, 106, 245, 145, 234, 152, 95, 136, 43, 129, 236, 253, 112, 144, 118, 19, 33, 243, 28, 150, 195, 247, 186, 146, 232, 249, 131, 2, 17, 0, 0, 0, 4, 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