Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 797f0dd3dca724b1fa6c9170e1a7e9838379b74e84603a463505e041aa1a5a6b

Tx prefix hash: 9ba32522f3c0a8e250f39ac6c8330a009a4569bb442914423338a581f204f0f9
Tx public key: a8319c58e78fab740fa00240f0bf4e887021335661be58ace710b853a975b4dc
Timestamp: 1584506789 Timestamp [UCT]: 2020-03-18 04:46:29 Age [y:d:h:m:s]: 05:069:14:24:35
Block: 84637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1206179 RingCT/type: yes/0
Extra: 01a8319c58e78fab740fa00240f0bf4e887021335661be58ace710b853a975b4dc021100000028c2c2f844000000000000000000

1 output(s) for total of 321.783126956000 dcy

stealth address amount amount idx
00: ae66f08a3cfd4b407f0c9bcbac3713133f6511410dd7739115bd2d7cdc09e1e8 321.783126956000 153321 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": 84647, "vin": [ { "gen": { "height": 84637 } } ], "vout": [ { "amount": 321783126956, "target": { "key": "ae66f08a3cfd4b407f0c9bcbac3713133f6511410dd7739115bd2d7cdc09e1e8" } } ], "extra": [ 1, 168, 49, 156, 88, 231, 143, 171, 116, 15, 160, 2, 64, 240, 191, 78, 136, 112, 33, 51, 86, 97, 190, 88, 172, 231, 16, 184, 83, 169, 117, 180, 220, 2, 17, 0, 0, 0, 40, 194, 194, 248, 68, 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