Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88319ae5bc34d73c3ae2428abb68782acf69b6134e056f6513f7774198783d58

Tx prefix hash: 913dfabeb1ec02c7ff389cbb4c639024857090c473e88741d1c252fc0e20b9fb
Tx public key: 909441edfea8fab8e5c714223974686d4b7c173ce5601ddcbefd80df925faab1
Timestamp: 1745984116 Timestamp [UCT]: 2025-04-30 03:35:16 Age [y:d:h:m:s]: 00:009:06:15:24
Block: 1272466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6615 RingCT/type: yes/0
Extra: 01909441edfea8fab8e5c714223974686d4b7c173ce5601ddcbefd80df925faab102110000000d9f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9eab7f5a4c026fd570bd782dd5ab32fd6aa63608af5053ecfbb0c11924c5db2 0.600000000000 1759741 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": 1272476, "vin": [ { "gen": { "height": 1272466 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9eab7f5a4c026fd570bd782dd5ab32fd6aa63608af5053ecfbb0c11924c5db2" } } ], "extra": [ 1, 144, 148, 65, 237, 254, 168, 250, 184, 229, 199, 20, 34, 57, 116, 104, 109, 75, 124, 23, 60, 229, 96, 29, 220, 190, 253, 128, 223, 146, 95, 170, 177, 2, 17, 0, 0, 0, 13, 159, 159, 230, 140, 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