Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e1fb8017ac515048eb6a182956ce945db3eba8ad8c0f0f2e205dbd69ea8502f

Tx prefix hash: 3ec34b455ca639ccf9692c6f4e18b3bd2252989ad49f5beaea6e33327775b013
Tx public key: dc3a79c0a072f84e9c72a336fa526f208cd7c4858b23af50f52541e499ab20e6
Timestamp: 1583752297 Timestamp [UCT]: 2020-03-09 11:11:37 Age [y:d:h:m:s]: 04:334:04:44:57
Block: 79283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1133459 RingCT/type: yes/0
Extra: 01dc3a79c0a072f84e9c72a336fa526f208cd7c4858b23af50f52541e499ab20e602110000000a6d997e00000000000000000000

1 output(s) for total of 335.199452081000 dcy

stealth address amount amount idx
00: 62da3138ee3ca4f72b649d7887f331433e1913b2b2f350eb991b7c13b564750b 335.199452081000 145075 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": 79293, "vin": [ { "gen": { "height": 79283 } } ], "vout": [ { "amount": 335199452081, "target": { "key": "62da3138ee3ca4f72b649d7887f331433e1913b2b2f350eb991b7c13b564750b" } } ], "extra": [ 1, 220, 58, 121, 192, 160, 114, 248, 78, 156, 114, 163, 54, 250, 82, 111, 32, 140, 215, 196, 133, 139, 35, 175, 80, 245, 37, 65, 228, 153, 171, 32, 230, 2, 17, 0, 0, 0, 10, 109, 153, 126, 0, 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