Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa59439742f6a1dda2e2df6ef3460c4b409d0868e90b0221c7a7736359322245

Tx prefix hash: 49e030a511f953c5bc331c49669acc9a1c2e2e36bdf57576f6f87edd4530bf6e
Tx public key: 68a335ec1eb1d5db7eaef7978a132b6ea60133043f4dc31060f8644cad909b4b
Timestamp: 1745202473 Timestamp [UCT]: 2025-04-21 02:27:53 Age [y:d:h:m:s]: 00:017:17:18:45
Block: 1265964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12686 RingCT/type: yes/0
Extra: 0168a335ec1eb1d5db7eaef7978a132b6ea60133043f4dc31060f8644cad909b4b0211000000096c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0dd704b66e3a0391e6863c2605dc3fd39ffb3d36c583123eadacaa13dbd0b710 0.600000000000 1753177 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": 1265974, "vin": [ { "gen": { "height": 1265964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0dd704b66e3a0391e6863c2605dc3fd39ffb3d36c583123eadacaa13dbd0b710" } } ], "extra": [ 1, 104, 163, 53, 236, 30, 177, 213, 219, 126, 174, 247, 151, 138, 19, 43, 110, 166, 1, 51, 4, 63, 77, 195, 16, 96, 248, 100, 76, 173, 144, 155, 75, 2, 17, 0, 0, 0, 9, 108, 152, 170, 61, 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