Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37ca4dcc48f08ce2c40f8b915b3362b6982ebb3fbe8f71e9f70bf57177bba890

Tx prefix hash: 050c02f5b8f364c1e4c99d8b4573fdc38f5fa4e2ed6e184c240b75e0b1a83ca5
Tx public key: dfbd5c9d9f836847372e7a962bdc2cea6d15d154235ee8074d25a189a2a07434
Timestamp: 1665882662 Timestamp [UCT]: 2022-10-16 01:11:02 Age [y:d:h:m:s]: 03:016:00:20:13
Block: 609931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 791681 RingCT/type: yes/0
Extra: 01dfbd5c9d9f836847372e7a962bdc2cea6d15d154235ee8074d25a189a2a0743402110000000175e3f0e9000000000000000000

1 output(s) for total of 5.848512842000 dcy

stealth address amount amount idx
00: 7004e6c0e37b9e03bfdcd9d0ebf022fbfa9361b2219a9326e5d99fb2bdbe24ec 5.848512842000 1046827 of 0

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": 609941, "vin": [ { "gen": { "height": 609931 } } ], "vout": [ { "amount": 5848512842, "target": { "key": "7004e6c0e37b9e03bfdcd9d0ebf022fbfa9361b2219a9326e5d99fb2bdbe24ec" } } ], "extra": [ 1, 223, 189, 92, 157, 159, 131, 104, 71, 55, 46, 122, 150, 43, 220, 44, 234, 109, 21, 209, 84, 35, 94, 232, 7, 77, 37, 161, 137, 162, 160, 116, 52, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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