Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55f3f1620723f9a77f73f81bb1c82f657e69279fbc1112e5b8ab0e44fad2d63b

Tx prefix hash: f5604e113c2b351ef8a8e8dfa5b6fb25836b8fec1f6eae4a35b572565eb8c865
Tx public key: 9507144c20f68f5f07309c7a77cb29533f6f55ae1e28e3c3f9244a33423687bb
Timestamp: 1706370335 Timestamp [UCT]: 2024-01-27 15:45:35 Age [y:d:h:m:s]: 01:142:16:27:58
Block: 944534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362987 RingCT/type: yes/0
Extra: 019507144c20f68f5f07309c7a77cb29533f6f55ae1e28e3c3f9244a33423687bb02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 341a16eae08fb82cc7c653c9bdac01ced41d0e83c7177385e5d5865fa9f1f692 0.600000000000 1402804 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": 944544, "vin": [ { "gen": { "height": 944534 } } ], "vout": [ { "amount": 600000000, "target": { "key": "341a16eae08fb82cc7c653c9bdac01ced41d0e83c7177385e5d5865fa9f1f692" } } ], "extra": [ 1, 149, 7, 20, 76, 32, 246, 143, 95, 7, 48, 156, 122, 119, 203, 41, 83, 63, 111, 85, 174, 30, 40, 227, 195, 249, 36, 74, 51, 66, 54, 135, 187, 2, 17, 0, 0, 0, 3, 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