Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8ee2d0cd4fb30aaaf3ba251a93c7ce49b358f794cda7ac8016490a36350a0b1

Tx prefix hash: a8e087696561e15c39e33bc82f655521faf1ccad44a46fa2c05750017ec3e38e
Tx public key: 73e7160526127e4b83300801642d0c0b759e5c5d5bab3968ca9d2a339db183dc
Timestamp: 1728951641 Timestamp [UCT]: 2024-10-15 00:20:41 Age [y:d:h:m:s]: 00:176:22:56:59
Block: 1131771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126245 RingCT/type: yes/0
Extra: 0173e7160526127e4b83300801642d0c0b759e5c5d5bab3968ca9d2a339db183dc021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75df26cef36618f21efd9dcc75ce73846970b63d957fe0a0e0100fd802ceee4c 0.600000000000 1614678 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": 1131781, "vin": [ { "gen": { "height": 1131771 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75df26cef36618f21efd9dcc75ce73846970b63d957fe0a0e0100fd802ceee4c" } } ], "extra": [ 1, 115, 231, 22, 5, 38, 18, 126, 75, 131, 48, 8, 1, 100, 45, 12, 11, 117, 158, 92, 93, 91, 171, 57, 104, 202, 157, 42, 51, 157, 177, 131, 220, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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