Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e452b780b190cbd8a653b1452f3a323eebf3828aa681b84161124166361faca

Tx prefix hash: 5683e3975b28f73a0a1b15de3d57ab7d27bf243c023ad66b52f6c6418f1d598c
Tx public key: 3bcbcd24eae9749df92194db135a14ea592ec001531e9ca9976effd3f772f1ce
Timestamp: 1580880098 Timestamp [UCT]: 2020-02-05 05:21:38 Age [y:d:h:m:s]: 05:115:04:18:18
Block: 58707 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1234696 RingCT/type: yes/0
Extra: 013bcbcd24eae9749df92194db135a14ea592ec001531e9ca9976effd3f772f1ce0211000000022264afe6000000000000000000

1 output(s) for total of 392.175228977000 dcy

stealth address amount amount idx
00: 9b233fcbd212c1b9fbe925403e66b8c688b1a512f1a6405410cc8749b7f81c3f 392.175228977000 108531 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": 58717, "vin": [ { "gen": { "height": 58707 } } ], "vout": [ { "amount": 392175228977, "target": { "key": "9b233fcbd212c1b9fbe925403e66b8c688b1a512f1a6405410cc8749b7f81c3f" } } ], "extra": [ 1, 59, 203, 205, 36, 234, 233, 116, 157, 249, 33, 148, 219, 19, 90, 20, 234, 89, 46, 192, 1, 83, 30, 156, 169, 151, 110, 255, 211, 247, 114, 241, 206, 2, 17, 0, 0, 0, 2, 34, 100, 175, 230, 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