Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 985af5d43953b3c829251655bb667948889ccd3b367358a209d8b6d46ee0f84f

Tx prefix hash: 2cca66f99018ee535c10201983df9ca5c23085ef389a5b452498bee18f200cb4
Tx public key: 2931c1d63a3ad752b4ebd3b844e92c1530dc9a5e1cd09d2584f8beedf1f7b70a
Timestamp: 1627599715 Timestamp [UCT]: 2021-07-29 23:01:55 Age [y:d:h:m:s]: 03:121:17:29:58
Block: 303461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 859489 RingCT/type: yes/0
Extra: 012931c1d63a3ad752b4ebd3b844e92c1530dc9a5e1cd09d2584f8beedf1f7b70a0211000000ad58045e5b000000000000000000

1 output(s) for total of 60.607067095000 dcy

stealth address amount amount idx
00: d81f508a82a92e83bae6f0145091d3b7b77d7a7ffcb5e27aadebf88396c0e08c 60.607067095000 633368 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": 303471, "vin": [ { "gen": { "height": 303461 } } ], "vout": [ { "amount": 60607067095, "target": { "key": "d81f508a82a92e83bae6f0145091d3b7b77d7a7ffcb5e27aadebf88396c0e08c" } } ], "extra": [ 1, 41, 49, 193, 214, 58, 58, 215, 82, 180, 235, 211, 184, 68, 233, 44, 21, 48, 220, 154, 94, 28, 208, 157, 37, 132, 248, 190, 237, 241, 247, 183, 10, 2, 17, 0, 0, 0, 173, 88, 4, 94, 91, 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