Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8a5acdf3165b7607f301bcb26118391ea825e4ef3a324f9efbe4d62d3908f93

Tx prefix hash: bd0f0c2a625a526d234334e54018fe19f5e06e7d52da15f5d27fcee99d8da5a4
Tx public key: 11ccf9aeb509f9eeee1cb635fb6d5033a6c2436d14789d1e7464b5579a819c66
Timestamp: 1688195281 Timestamp [UCT]: 2023-07-01 07:08:01 Age [y:d:h:m:s]: 02:130:11:16:12
Block: 794136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 612970 RingCT/type: yes/0
Extra: 0111ccf9aeb509f9eeee1cb635fb6d5033a6c2436d14789d1e7464b5579a819c6602110000000375e3f0e9000000000000000000

1 output(s) for total of 1.434491268000 dcy

stealth address amount amount idx
00: 020d8aca7f0257acbf4fabcc6f7aa3819d4b500f328fa155168845a5e48db0be 1.434491268000 1244861 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": 794146, "vin": [ { "gen": { "height": 794136 } } ], "vout": [ { "amount": 1434491268, "target": { "key": "020d8aca7f0257acbf4fabcc6f7aa3819d4b500f328fa155168845a5e48db0be" } } ], "extra": [ 1, 17, 204, 249, 174, 181, 9, 249, 238, 238, 28, 182, 53, 251, 109, 80, 51, 166, 194, 67, 109, 20, 120, 157, 30, 116, 100, 181, 87, 154, 129, 156, 102, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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