Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe9cc4ea9a348a34fe0be5141ffd868800027818fe945ff9a95dbc59078c5d4d

Tx prefix hash: a90bacb7caad837f914a37ba7685b04fbafa60816e9bdaade07cc8b62ec99f1a
Tx public key: a6ce5412aace9503aeef4da7cbcdb5e61cc05181bc926719cbc034c7f3b2018a
Timestamp: 1578633468 Timestamp [UCT]: 2020-01-10 05:17:48 Age [y:d:h:m:s]: 05:299:19:58:30
Block: 42224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1362229 RingCT/type: yes/0
Extra: 01a6ce5412aace9503aeef4da7cbcdb5e61cc05181bc926719cbc034c7f3b2018a0211000000098a2ee0d9000000000000000000

1 output(s) for total of 444.789458503000 dcy

stealth address amount amount idx
00: 4bd4bdcfcb6f9de72e320e9a52d554ce95cca4ec01bffd492e57e9755b7b0097 444.789458503000 75978 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": 42234, "vin": [ { "gen": { "height": 42224 } } ], "vout": [ { "amount": 444789458503, "target": { "key": "4bd4bdcfcb6f9de72e320e9a52d554ce95cca4ec01bffd492e57e9755b7b0097" } } ], "extra": [ 1, 166, 206, 84, 18, 170, 206, 149, 3, 174, 239, 77, 167, 203, 205, 181, 230, 28, 192, 81, 129, 188, 146, 103, 25, 203, 192, 52, 199, 243, 178, 1, 138, 2, 17, 0, 0, 0, 9, 138, 46, 224, 217, 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