Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9f5958a0407b6c8093256962a457d1d8c61f3dd8465e9be0fc82a0db4300489

Tx prefix hash: aa7efe552065a8babb1a6f5001f2c316e4a5a12ab0b4a8d1edd870d38a57c66a
Tx public key: 14f2f286bcd7bdb9c4fbba7beeddc5fafe624e6a1c22a1686a5d59e68e1423cd
Timestamp: 1711516115 Timestamp [UCT]: 2024-03-27 05:08:35 Age [y:d:h:m:s]: 00:334:13:00:57
Block: 987247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239138 RingCT/type: yes/0
Extra: 0114f2f286bcd7bdb9c4fbba7beeddc5fafe624e6a1c22a1686a5d59e68e1423cd02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 166d451e204448574f28a54e4c6e96503b9cc4e66daee369ac08dca06aed78e4 0.600000000000 1447488 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": 987257, "vin": [ { "gen": { "height": 987247 } } ], "vout": [ { "amount": 600000000, "target": { "key": "166d451e204448574f28a54e4c6e96503b9cc4e66daee369ac08dca06aed78e4" } } ], "extra": [ 1, 20, 242, 242, 134, 188, 215, 189, 185, 196, 251, 186, 123, 238, 221, 197, 250, 254, 98, 78, 106, 28, 34, 161, 104, 106, 93, 89, 230, 142, 20, 35, 205, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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