Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbc21a8fa036ee9b9f2ec6982f836fea3bed0e823bfa9789f1b83c156a416927

Tx prefix hash: 7cd92eb249cc712cfe4a2528029facc763f5b4dc9152a5463601c57a5fdefac1
Tx public key: 71ec2f4ad1e5f8e57dc9605f5351dead31c785a69319de92a53a0fe78abce355
Timestamp: 1672685211 Timestamp [UCT]: 2023-01-02 18:46:51 Age [y:d:h:m:s]: 02:104:07:01:21
Block: 666163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 596231 RingCT/type: yes/0
Extra: 0171ec2f4ad1e5f8e57dc9605f5351dead31c785a69319de92a53a0fe78abce35502110000000752542ceb000000000000000000

1 output(s) for total of 3.808249611000 dcy

stealth address amount amount idx
00: eb4001dfab698e6ba35e026515a79a17453494721f81ff46be73cde05d0f6e45 3.808249611000 1107262 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": 666173, "vin": [ { "gen": { "height": 666163 } } ], "vout": [ { "amount": 3808249611, "target": { "key": "eb4001dfab698e6ba35e026515a79a17453494721f81ff46be73cde05d0f6e45" } } ], "extra": [ 1, 113, 236, 47, 74, 209, 229, 248, 229, 125, 201, 96, 95, 83, 81, 222, 173, 49, 199, 133, 166, 147, 25, 222, 146, 165, 58, 15, 231, 138, 188, 227, 85, 2, 17, 0, 0, 0, 7, 82, 84, 44, 235, 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