Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57620e290b874620844ea56be0c499f2ed9aeadfdbeab4426d6c301cc83e3b52

Tx prefix hash: 8b8220b40849e0cab4b5d747407dbe2ca0a9168f5c9382aada80eb22b5659bf6
Tx public key: e36cd4c8b49bb23911a7423e12d0b59890e68687baaa4a6ca2bbe0a1273fcf06
Timestamp: 1737195826 Timestamp [UCT]: 2025-01-18 10:23:46 Age [y:d:h:m:s]: 00:154:01:38:04
Block: 1199968 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109770 RingCT/type: yes/0
Extra: 01e36cd4c8b49bb23911a7423e12d0b59890e68687baaa4a6ca2bbe0a1273fcf060211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 359289750b6d0dc25ab6bd176fb3bce357dc518300756b386c4b55c0280cfc6f 0.600000000000 1686609 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": 1199978, "vin": [ { "gen": { "height": 1199968 } } ], "vout": [ { "amount": 600000000, "target": { "key": "359289750b6d0dc25ab6bd176fb3bce357dc518300756b386c4b55c0280cfc6f" } } ], "extra": [ 1, 227, 108, 212, 200, 180, 155, 178, 57, 17, 167, 66, 62, 18, 208, 181, 152, 144, 230, 134, 135, 186, 170, 74, 108, 162, 187, 224, 161, 39, 63, 207, 6, 2, 17, 0, 0, 0, 6, 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