Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 886f7768e2292cb73f5da88074c7234a3064ffd6e96c28cd6f097a332849d1bd

Tx prefix hash: fc9ccb5d94a863383b22eb47a85eab2f2b7c45a2521f91d64b4c60c353a109b1
Tx public key: aa1595ee17d651fe5769d014d86d71cbf0868203592d62667c9b5662c5a89d3b
Timestamp: 1730606870 Timestamp [UCT]: 2024-11-03 04:07:50 Age [y:d:h:m:s]: 00:021:09:52:19
Block: 1145401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15334 RingCT/type: yes/0
Extra: 01aa1595ee17d651fe5769d014d86d71cbf0868203592d62667c9b5662c5a89d3b0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fff9a9dd5adb0971a11f9998b7e254fd4d01a59d27a04ed408df36057e2fb23 0.600000000000 1629832 of 15

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": 1145411, "vin": [ { "gen": { "height": 1145401 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fff9a9dd5adb0971a11f9998b7e254fd4d01a59d27a04ed408df36057e2fb23" } } ], "extra": [ 1, 170, 21, 149, 238, 23, 214, 81, 254, 87, 105, 208, 20, 216, 109, 113, 203, 240, 134, 130, 3, 89, 45, 98, 102, 124, 155, 86, 98, 197, 168, 157, 59, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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