Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b07401d389580deaf0722317e208c502d3d293a61406b4699f97027caa195705

Tx prefix hash: 595398c5ae85f81539576fd05b8407c4a1e823f56b2c9eee50f282ecad7374a5
Tx public key: d3d9ef7cdb5f2463b8690abb70c78ec4acc21d766058aaf7756dc76428d4a61a
Timestamp: 1580589623 Timestamp [UCT]: 2020-02-01 20:40:23 Age [y:d:h:m:s]: 04:300:05:38:17
Block: 56752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1105771 RingCT/type: yes/0
Extra: 01d3d9ef7cdb5f2463b8690abb70c78ec4acc21d766058aaf7756dc76428d4a61a02110000000d4ac5aa02000000000000000000

1 output(s) for total of 398.068569577000 dcy

stealth address amount amount idx
00: 7225a296f40dcc0e8ab0ff0c62ca5c28e9d653881d6f9974a2f831f6d3d93666 398.068569577000 104633 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": 56762, "vin": [ { "gen": { "height": 56752 } } ], "vout": [ { "amount": 398068569577, "target": { "key": "7225a296f40dcc0e8ab0ff0c62ca5c28e9d653881d6f9974a2f831f6d3d93666" } } ], "extra": [ 1, 211, 217, 239, 124, 219, 95, 36, 99, 184, 105, 10, 187, 112, 199, 142, 196, 172, 194, 29, 118, 96, 88, 170, 247, 117, 109, 199, 100, 40, 212, 166, 26, 2, 17, 0, 0, 0, 13, 74, 197, 170, 2, 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