Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa26038e8f5a5edcdd57f8283cc9bc85528522cd375fb740359d4fd61764dcdf

Tx prefix hash: e144082611d1a8331843433e4cb448b1da4ae9d31124f16dc185cc10829e941e
Tx public key: fd7ad477e0f8b49205f726ea6cc40a448081a7a5adb3de7b46886408fba26683
Timestamp: 1715314758 Timestamp [UCT]: 2024-05-10 04:19:18 Age [y:d:h:m:s]: 01:006:10:07:55
Block: 1018715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265511 RingCT/type: yes/0
Extra: 01fd7ad477e0f8b49205f726ea6cc40a448081a7a5adb3de7b46886408fba2668302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3adc8c6735b306ca934a04014445f7584f9ecb030aa7e6cfcf8d24b3cbebb3d7 0.600000000000 1482508 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": 1018725, "vin": [ { "gen": { "height": 1018715 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3adc8c6735b306ca934a04014445f7584f9ecb030aa7e6cfcf8d24b3cbebb3d7" } } ], "extra": [ 1, 253, 122, 212, 119, 224, 248, 180, 146, 5, 247, 38, 234, 108, 196, 10, 68, 128, 129, 167, 165, 173, 179, 222, 123, 70, 136, 100, 8, 251, 162, 102, 131, 2, 17, 0, 0, 0, 2, 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