Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45c6380c850f26b6579215fdce705592d3b32a0f0ebc378623b0c4c71e60a122

Tx prefix hash: 5d0860896dd19baf39e6f66f73c48e8e4c62c6083c5974722981fc03a7b35863
Tx public key: 7807a4c269c7285b466dba1190d0b7a53b48aad9b2a6dcdadae6e73247c65b09
Timestamp: 1738773462 Timestamp [UCT]: 2025-02-05 16:37:42 Age [y:d:h:m:s]: 00:280:19:47:49
Block: 1212763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198464 RingCT/type: yes/0
Extra: 017807a4c269c7285b466dba1190d0b7a53b48aad9b2a6dcdadae6e73247c65b090211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 970572a1f2ea6d3fc8bf7e95981dda55be8e8ef42128c10e1d0451c992d49c4c 0.600000000000 1699538 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": 1212773, "vin": [ { "gen": { "height": 1212763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "970572a1f2ea6d3fc8bf7e95981dda55be8e8ef42128c10e1d0451c992d49c4c" } } ], "extra": [ 1, 120, 7, 164, 194, 105, 199, 40, 91, 70, 109, 186, 17, 144, 208, 183, 165, 59, 72, 170, 217, 178, 166, 220, 218, 218, 230, 231, 50, 71, 198, 91, 9, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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