Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec33e9d2a49bfc7c181ca370fafc7d8aa9d3e7bed855f365f3bee90e1a8c68bf

Tx prefix hash: 339d77675083c4cc43f48f1c29c409efceaed754c10feeb4143fe4bb9261ad0c
Tx public key: 8cee93242151cdd1ef9593b8d0154ef63d197b02b289b77ea6069b31ca65cb6f
Timestamp: 1752109406 Timestamp [UCT]: 2025-07-10 01:03:26 Age [y:d:h:m:s]: 00:174:15:42:48
Block: 1322281 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123443 RingCT/type: yes/0
Extra: 018cee93242151cdd1ef9593b8d0154ef63d197b02b289b77ea6069b31ca65cb6f021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09ec0ffd12be465d9488dfcf2f54f0d41399358087a7a343e08fbe9ddb860f55 0.600000000000 1810008 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": 1322291, "vin": [ { "gen": { "height": 1322281 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09ec0ffd12be465d9488dfcf2f54f0d41399358087a7a343e08fbe9ddb860f55" } } ], "extra": [ 1, 140, 238, 147, 36, 33, 81, 205, 209, 239, 149, 147, 184, 208, 21, 78, 246, 61, 25, 123, 2, 178, 137, 183, 126, 166, 6, 155, 49, 202, 101, 203, 111, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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