Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5868f852ba410c482bb5489533df913864b107460849c4c64c8f00b8bc8c9a24

Tx prefix hash: 14a7bc419cd2bd6d3de28d884d40f159cef995cba7cc33bd1a16f33ff44db0e0
Tx public key: e6d77e4d0929d2774873635fbbf5ac51f6d7b86e037c985d4961cd7692b08da9
Timestamp: 1719488465 Timestamp [UCT]: 2024-06-27 11:41:05 Age [y:d:h:m:s]: 01:135:10:24:10
Block: 1053311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355346 RingCT/type: yes/0
Extra: 01e6d77e4d0929d2774873635fbbf5ac51f6d7b86e037c985d4961cd7692b08da90211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51b2bf30e510a55f8d0d89452a87952132cdd7a2bf985b39e72bf7bf177546ee 0.600000000000 1523658 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": 1053321, "vin": [ { "gen": { "height": 1053311 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51b2bf30e510a55f8d0d89452a87952132cdd7a2bf985b39e72bf7bf177546ee" } } ], "extra": [ 1, 230, 215, 126, 77, 9, 41, 210, 119, 72, 115, 99, 95, 187, 245, 172, 81, 246, 215, 184, 110, 3, 124, 152, 93, 73, 97, 205, 118, 146, 176, 141, 169, 2, 17, 0, 0, 0, 8, 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