Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60c04b9175749e9ceb469820957cfeba5f8e17bbec766f6de2d35e3dea68f7af

Tx prefix hash: fe6b0df1c12a7649a6109dbbf694867b3fe6a346b97c0d92e76bd617ad5fa6dc
Tx public key: 8ba2df95b8803289ef37c1d46f49ba0f817992e6969049b659821e794027a0b2
Timestamp: 1638823373 Timestamp [UCT]: 2021-12-06 20:42:53 Age [y:d:h:m:s]: 02:334:12:47:33
Block: 389900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 757096 RingCT/type: yes/0
Extra: 018ba2df95b8803289ef37c1d46f49ba0f817992e6969049b659821e794027a0b2021100000002e59f5d07000000000000000000

1 output(s) for total of 31.340059094000 dcy

stealth address amount amount idx
00: 832f87f9288609f9971ba199ce139ad51a3061e3a991ada4876ac199fbcd9566 31.340059094000 785355 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": 389910, "vin": [ { "gen": { "height": 389900 } } ], "vout": [ { "amount": 31340059094, "target": { "key": "832f87f9288609f9971ba199ce139ad51a3061e3a991ada4876ac199fbcd9566" } } ], "extra": [ 1, 139, 162, 223, 149, 184, 128, 50, 137, 239, 55, 193, 212, 111, 73, 186, 15, 129, 121, 146, 230, 150, 144, 73, 182, 89, 130, 30, 121, 64, 39, 160, 178, 2, 17, 0, 0, 0, 2, 229, 159, 93, 7, 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