Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8df3730d9b12320dfd2a16b87aeb3a053dc30eb4ab1115ddaca6f85e7ea2aa06

Tx prefix hash: 40e213748a227f5df474b30fd8177c5dc363cf3bcbf236c6b996fc78502fcddd
Tx public key: 40a7b88393f98dc15d6868adc0c9063f34f7c7fe06a29f437fc27e1f509bcf30
Timestamp: 1704714523 Timestamp [UCT]: 2024-01-08 11:48:43 Age [y:d:h:m:s]: 01:087:02:57:36
Block: 930814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323381 RingCT/type: yes/0
Extra: 0140a7b88393f98dc15d6868adc0c9063f34f7c7fe06a29f437fc27e1f509bcf300211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc06eaa7485c2933a21c781ce05d37e8d0385ef9cb1643affc3f0e17db92ae47 0.600000000000 1388704 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": 930824, "vin": [ { "gen": { "height": 930814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc06eaa7485c2933a21c781ce05d37e8d0385ef9cb1643affc3f0e17db92ae47" } } ], "extra": [ 1, 64, 167, 184, 131, 147, 249, 141, 193, 93, 104, 104, 173, 192, 201, 6, 63, 52, 247, 199, 254, 6, 162, 159, 67, 127, 194, 126, 31, 80, 155, 207, 48, 2, 17, 0, 0, 0, 4, 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