Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f38f304f9cc87596dc28c0ca90270a0e6d25d30b1afe80bc48ba3c8dc9ace418

Tx prefix hash: c9b5c408866934249fb593f3c461efb4bb35d3d9762aab981c228324bfdece49
Tx public key: 37b4522ae5ab3000e959f52ecfb4d1fa3d73b974d66972228d4fa64e854a6f45
Timestamp: 1754454843 Timestamp [UCT]: 2025-08-06 04:34:03 Age [y:d:h:m:s]: 00:106:23:27:50
Block: 1341249 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75441 RingCT/type: yes/0
Extra: 0137b4522ae5ab3000e959f52ecfb4d1fa3d73b974d66972228d4fa64e854a6f450211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1313ee6da1dafaf3a64600d0dd4f14f47b2b1a1a7c6bb101e6a561e04324f918 0.600000000000 1829072 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": 1341259, "vin": [ { "gen": { "height": 1341249 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1313ee6da1dafaf3a64600d0dd4f14f47b2b1a1a7c6bb101e6a561e04324f918" } } ], "extra": [ 1, 55, 180, 82, 42, 229, 171, 48, 0, 233, 89, 245, 46, 207, 180, 209, 250, 61, 115, 185, 116, 214, 105, 114, 34, 141, 79, 166, 78, 133, 74, 111, 69, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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