Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3afb6028c057122a992a7fb469cfdf9e202c0d0b18784e8c63eb2b9a0572dfde

Tx prefix hash: 0e47e0e09000e2cc090c4935a31c8e0fe299bc0b373d97323cbe9d0569539519
Tx public key: bbc38afa7298396abf196f713708826db1aa88fb5063b4c1117d484d13e67e96
Timestamp: 1705268139 Timestamp [UCT]: 2024-01-14 21:35:39 Age [y:d:h:m:s]: 01:067:14:37:18
Block: 935400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309423 RingCT/type: yes/0
Extra: 01bbc38afa7298396abf196f713708826db1aa88fb5063b4c1117d484d13e67e960211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: faefc69ca6adaf4e8b580e230d37955d9530935f61bca76bbf0ad886e0e5ac0b 0.600000000000 1393416 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": 935410, "vin": [ { "gen": { "height": 935400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "faefc69ca6adaf4e8b580e230d37955d9530935f61bca76bbf0ad886e0e5ac0b" } } ], "extra": [ 1, 187, 195, 138, 250, 114, 152, 57, 106, 191, 25, 111, 113, 55, 8, 130, 109, 177, 170, 136, 251, 80, 99, 180, 193, 17, 125, 72, 77, 19, 230, 126, 150, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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