Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 856b11628fde1302df6805d47ba055c9f0c1246e008f9998f0e7116efcd3593d

Tx prefix hash: 62d289857bc7785786253f2c60a747f6da20b5bf9250f7b8f5fb85588c9e8df8
Tx public key: 3b8f845bb2cd47a1ace2c3a4ff7fd1a033258c057f8c60e55498ac5a996ea483
Timestamp: 1682231156 Timestamp [UCT]: 2023-04-23 06:25:56 Age [y:d:h:m:s]: 01:274:17:30:11
Block: 744684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457794 RingCT/type: yes/0
Extra: 013b8f845bb2cd47a1ace2c3a4ff7fd1a033258c057f8c60e55498ac5a996ea483021100000002faf35c9c000000000000000000

1 output(s) for total of 2.091958120000 dcy

stealth address amount amount idx
00: 678a0b4ad8d8df33be7c49bc95743833c8fa813ca6ea8645bb85c45311c30ca7 2.091958120000 1192051 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": 744694, "vin": [ { "gen": { "height": 744684 } } ], "vout": [ { "amount": 2091958120, "target": { "key": "678a0b4ad8d8df33be7c49bc95743833c8fa813ca6ea8645bb85c45311c30ca7" } } ], "extra": [ 1, 59, 143, 132, 91, 178, 205, 71, 161, 172, 226, 195, 164, 255, 127, 209, 160, 51, 37, 140, 5, 127, 140, 96, 229, 84, 152, 172, 90, 153, 110, 164, 131, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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