Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 381e47a47259001e0875f9928db1d4778df759f6d8b663d02e3ab8a3412095a6

Tx prefix hash: 825656af6dbd6e9b73d421dffaf794c0e37f7a94a1892058876a65ad85f4af9c
Tx public key: c4a069a41d1594716d6a8a8500a85f9c0b56ba7d3f749d29a41a304acb9c8f99
Timestamp: 1721183538 Timestamp [UCT]: 2024-07-17 02:32:18 Age [y:d:h:m:s]: 00:194:17:18:49
Block: 1067379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139058 RingCT/type: yes/0
Extra: 01c4a069a41d1594716d6a8a8500a85f9c0b56ba7d3f749d29a41a304acb9c8f9902110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5cf4344cad4b1a3d638ce96277c782c0ad4fbb83ae961dcc151d380cf36efe2 0.600000000000 1538176 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": 1067389, "vin": [ { "gen": { "height": 1067379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5cf4344cad4b1a3d638ce96277c782c0ad4fbb83ae961dcc151d380cf36efe2" } } ], "extra": [ 1, 196, 160, 105, 164, 29, 21, 148, 113, 109, 106, 138, 133, 0, 168, 95, 156, 11, 86, 186, 125, 63, 116, 157, 41, 164, 26, 48, 74, 203, 156, 143, 153, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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