Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a17b8bf8fc60ba8357b8ecc5abe64f673e64e4393700bbb0fe177887e56bc55a

Tx prefix hash: f03e9945c9d3178575158be5d268336e353c8047e60b5a9101f1e26e0c0579ff
Tx public key: 1c918a812fd7ce9c8f3019ab9cafea97aecd7b3edd5e223cb67ee6f1e13e678f
Timestamp: 1718311580 Timestamp [UCT]: 2024-06-13 20:46:20 Age [y:d:h:m:s]: 00:343:15:28:11
Block: 1043560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245617 RingCT/type: yes/0
Extra: 011c918a812fd7ce9c8f3019ab9cafea97aecd7b3edd5e223cb67ee6f1e13e678f02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3e566b63c890ec656a1146df9a95bd14180172175d4fb15dbfbb0d6cb8446ed 0.600000000000 1512715 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": 1043570, "vin": [ { "gen": { "height": 1043560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3e566b63c890ec656a1146df9a95bd14180172175d4fb15dbfbb0d6cb8446ed" } } ], "extra": [ 1, 28, 145, 138, 129, 47, 215, 206, 156, 143, 48, 25, 171, 156, 175, 234, 151, 174, 205, 123, 62, 221, 94, 34, 60, 182, 126, 230, 241, 225, 62, 103, 143, 2, 17, 0, 0, 0, 4, 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