Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9908350da42f6b4964af8546e0f81123cfaa42002fa168f4d9d16c5b7d82a9e1

Tx prefix hash: 78d94dabe40963f4f86e8272f4b3e396ee83d4386467cae20110b3d58dc317af
Tx public key: 3bf86be919faa1fb2e2f633e9013ee974f3d27acaff0d14f0d2b4ab28477a88b
Timestamp: 1674355042 Timestamp [UCT]: 2023-01-22 02:37:22 Age [y:d:h:m:s]: 01:356:13:03:25
Block: 680005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 515831 RingCT/type: yes/0
Extra: 013bf86be919faa1fb2e2f633e9013ee974f3d27acaff0d14f0d2b4ab28477a88b021100000004272bcc39000000000000000000

1 output(s) for total of 3.426581723000 dcy

stealth address amount amount idx
00: b9eb84e2254204d3fe99593f4a6661d22507c41669ac85d989d76e3dc7add17c 3.426581723000 1122028 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": 680015, "vin": [ { "gen": { "height": 680005 } } ], "vout": [ { "amount": 3426581723, "target": { "key": "b9eb84e2254204d3fe99593f4a6661d22507c41669ac85d989d76e3dc7add17c" } } ], "extra": [ 1, 59, 248, 107, 233, 25, 250, 161, 251, 46, 47, 99, 62, 144, 19, 238, 151, 79, 61, 39, 172, 175, 240, 209, 79, 13, 43, 74, 178, 132, 119, 168, 139, 2, 17, 0, 0, 0, 4, 39, 43, 204, 57, 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