Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d991ac419950d27a8df56c87f9c564612b1086dc4fc10ef1472200ad48799145

Tx prefix hash: ff41b50a254dfb30605ea487ebd4bece80b3bb516366d46217d17207db150862
Tx public key: 3caf6bbaac872a35c43cc99ad23b8adf18b75e2c9767a11ac20d6bef0d6aba4c
Timestamp: 1704240448 Timestamp [UCT]: 2024-01-03 00:07:28 Age [y:d:h:m:s]: 01:164:21:32:18
Block: 926891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378914 RingCT/type: yes/0
Extra: 013caf6bbaac872a35c43cc99ad23b8adf18b75e2c9767a11ac20d6bef0d6aba4c02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 403f0d919a3903aa71a4f971036a96908b2236a6d4fe7be5a0e1f125c1caae73 0.600000000000 1384691 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": 926901, "vin": [ { "gen": { "height": 926891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "403f0d919a3903aa71a4f971036a96908b2236a6d4fe7be5a0e1f125c1caae73" } } ], "extra": [ 1, 60, 175, 107, 186, 172, 135, 42, 53, 196, 60, 201, 154, 210, 59, 138, 223, 24, 183, 94, 44, 151, 103, 161, 26, 194, 13, 107, 239, 13, 106, 186, 76, 2, 17, 0, 0, 0, 1, 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