Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09db354231a62a79282f696d12c1d707a39c0384492811eaed1f0386866e2ad9

Tx prefix hash: 8b06811f1ca5bb3d00fd02e611e70d5bcb754fe807ff85658b851b3ed0937bdf
Tx public key: 8ab71df422e02ef9373d6d0669f7c60d7a0d84c15d7352d543c496c5487d3de7
Timestamp: 1702131587 Timestamp [UCT]: 2023-12-09 14:19:47 Age [y:d:h:m:s]: 01:038:21:38:08
Block: 909412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289171 RingCT/type: yes/0
Extra: 018ab71df422e02ef9373d6d0669f7c60d7a0d84c15d7352d543c496c5487d3de7021100000004faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51effcaabffcb4b5bd6202670ec51bf3c1cf7343bb6ddca53846cd3b999dc072 0.600000000000 1366499 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": 909422, "vin": [ { "gen": { "height": 909412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51effcaabffcb4b5bd6202670ec51bf3c1cf7343bb6ddca53846cd3b999dc072" } } ], "extra": [ 1, 138, 183, 29, 244, 34, 224, 46, 249, 55, 61, 109, 6, 105, 247, 198, 13, 122, 13, 132, 193, 93, 115, 82, 213, 67, 196, 150, 197, 72, 125, 61, 231, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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