Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02e6116b3455291bba4c8475e2aec779c0721baff7e96cb48193ef81885d20f7

Tx prefix hash: 4ac340221c6dca02a59797c025c204191166c93187f3c57b4e4a86bafec07d48
Tx public key: c8a7dff99c323a3a4560c022f30c77355e1d8d4d9d15bb2f90e3e52e5881aac3
Timestamp: 1635064754 Timestamp [UCT]: 2021-10-24 08:39:14 Age [y:d:h:m:s]: 03:142:06:48:01
Block: 359385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 879825 RingCT/type: yes/0
Extra: 01c8a7dff99c323a3a4560c022f30c77355e1d8d4d9d15bb2f90e3e52e5881aac3021100000005f29d7abf000000000000000000

1 output(s) for total of 39.555667447000 dcy

stealth address amount amount idx
00: 58f88aea4d5e5437341c2980c01a27715e4f6a55cf1408e73747bd8dc1f093e5 39.555667447000 731870 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": 359395, "vin": [ { "gen": { "height": 359385 } } ], "vout": [ { "amount": 39555667447, "target": { "key": "58f88aea4d5e5437341c2980c01a27715e4f6a55cf1408e73747bd8dc1f093e5" } } ], "extra": [ 1, 200, 167, 223, 249, 156, 50, 58, 58, 69, 96, 192, 34, 243, 12, 119, 53, 94, 29, 141, 77, 157, 21, 187, 47, 144, 227, 229, 46, 88, 129, 170, 195, 2, 17, 0, 0, 0, 5, 242, 157, 122, 191, 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