Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edd9da54015849aa217fb63ffefaab7cbb9b94be5eac960dd4fddef4dae2e53b

Tx prefix hash: 6b204ca21f680d4d2ff7df5a73e2a0c172cae673e385e9465f9dd68bc6e1c1a9
Tx public key: 19f3b8cb236209c745659325bfde833d4633c6fc5709512ff2e086b8cdcb8041
Timestamp: 1738171230 Timestamp [UCT]: 2025-01-29 17:20:30 Age [y:d:h:m:s]: 00:296:06:10:34
Block: 1207792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 209488 RingCT/type: yes/0
Extra: 0119f3b8cb236209c745659325bfde833d4633c6fc5709512ff2e086b8cdcb80410211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36c84873325c6ab4ea4490928d829bbea74407273d522fa9994354b963fac74c 0.600000000000 1694517 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": 1207802, "vin": [ { "gen": { "height": 1207792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36c84873325c6ab4ea4490928d829bbea74407273d522fa9994354b963fac74c" } } ], "extra": [ 1, 25, 243, 184, 203, 35, 98, 9, 199, 69, 101, 147, 37, 191, 222, 131, 61, 70, 51, 198, 252, 87, 9, 81, 47, 242, 224, 134, 184, 205, 203, 128, 65, 2, 17, 0, 0, 0, 2, 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