Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d665787a370e911fb9c5a8608d3c4fcce34643f4618cf15e77cc41b9dc2d14b

Tx prefix hash: 7717a198a5c0c797ccb7609fed4b92535757cf538fefd3fb251e1a5ae29e4269
Tx public key: ddc16c41fb7ede6884bb561671573b295f414afb493dd1d7c6ce663c604ab37d
Timestamp: 1718969398 Timestamp [UCT]: 2024-06-21 11:29:58 Age [y:d:h:m:s]: 00:291:21:58:48
Block: 1048989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208622 RingCT/type: yes/0
Extra: 01ddc16c41fb7ede6884bb561671573b295f414afb493dd1d7c6ce663c604ab37d02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28ae66facbdcc6089a4fe44bd09210a116c09541e99ca6e68db9f37afb0230a8 0.600000000000 1519086 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": 1048999, "vin": [ { "gen": { "height": 1048989 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28ae66facbdcc6089a4fe44bd09210a116c09541e99ca6e68db9f37afb0230a8" } } ], "extra": [ 1, 221, 193, 108, 65, 251, 126, 222, 104, 132, 187, 86, 22, 113, 87, 59, 41, 95, 65, 74, 251, 73, 61, 209, 215, 198, 206, 102, 60, 96, 74, 179, 125, 2, 17, 0, 0, 0, 3, 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