Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 431cd0cbcd4a0e848855543fb93bf07b6a29c01b2d160db36cf68335688f1e01

Tx prefix hash: d26866258e642059868a9e97994895232c25431350945ae458139908e74e9e01
Tx public key: 1d211ac4f2fe39809e095f276c0c8ef16f5b13cad11faa4df02f24916a5e9aea
Timestamp: 1581243846 Timestamp [UCT]: 2020-02-09 10:24:06 Age [y:d:h:m:s]: 04:297:15:34:30
Block: 61221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1104878 RingCT/type: yes/0
Extra: 011d211ac4f2fe39809e095f276c0c8ef16f5b13cad11faa4df02f24916a5e9aea0211000001a5c71d3ff9000000000000000000

1 output(s) for total of 384.724841585000 dcy

stealth address amount amount idx
00: c9b086ef1394dd4f6d00d3243ca4277b712eff937ccc6a6db7d6650768565bf0 384.724841585000 112812 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": 61231, "vin": [ { "gen": { "height": 61221 } } ], "vout": [ { "amount": 384724841585, "target": { "key": "c9b086ef1394dd4f6d00d3243ca4277b712eff937ccc6a6db7d6650768565bf0" } } ], "extra": [ 1, 29, 33, 26, 196, 242, 254, 57, 128, 158, 9, 95, 39, 108, 12, 142, 241, 111, 91, 19, 202, 209, 31, 170, 77, 240, 47, 36, 145, 106, 94, 154, 234, 2, 17, 0, 0, 1, 165, 199, 29, 63, 249, 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