Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 857a2fe6de3263859cf0b91fbefdddcf24641f2dfaf0d1c7b9f1c10137a21a6a

Tx prefix hash: 203e6e1d2c4bb1efd36391bc3bb0f4872eb0050b0567f76be438233758d3e72f
Tx public key: d31080f76aef7b8d74a6bdb384f82c461ab4f445516183ca648c4d54cd1a1427
Timestamp: 1677603626 Timestamp [UCT]: 2023-02-28 17:00:26 Age [y:d:h:m:s]: 01:254:13:40:47
Block: 706949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442834 RingCT/type: yes/0
Extra: 01d31080f76aef7b8d74a6bdb384f82c461ab4f445516183ca648c4d54cd1a142702110000000475e3f0e9000000000000000000

1 output(s) for total of 2.789872767000 dcy

stealth address amount amount idx
00: cc707c74fad0060f2fd72643f34252693bd9005f435c71764faca06dbb8cac98 2.789872767000 1150734 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": 706959, "vin": [ { "gen": { "height": 706949 } } ], "vout": [ { "amount": 2789872767, "target": { "key": "cc707c74fad0060f2fd72643f34252693bd9005f435c71764faca06dbb8cac98" } } ], "extra": [ 1, 211, 16, 128, 247, 106, 239, 123, 141, 116, 166, 189, 179, 132, 248, 44, 70, 26, 180, 244, 69, 81, 97, 131, 202, 100, 140, 77, 84, 205, 26, 20, 39, 2, 17, 0, 0, 0, 4, 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