Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5a1f90573a64da24dcf98755a51c8e51d373449fa5aa496a036b99477af84c2

Tx prefix hash: 1cc04b266a59aab84e2f6abce6a09a243534cd95fb3358bbb683271d197a4e08
Tx public key: 0cf48afbe2d1376476ae75f4a5856de6b6f2bd6d8f472846287e093f709eff9a
Timestamp: 1737753485 Timestamp [UCT]: 2025-01-24 21:18:05 Age [y:d:h:m:s]: 00:144:18:44:23
Block: 1204535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103226 RingCT/type: yes/0
Extra: 010cf48afbe2d1376476ae75f4a5856de6b6f2bd6d8f472846287e093f709eff9a021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53d5dac3750409cb19bcbdb06d20888b0fb3f26cb377229425f5eb7b2e1e619e 0.600000000000 1691222 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": 1204545, "vin": [ { "gen": { "height": 1204535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53d5dac3750409cb19bcbdb06d20888b0fb3f26cb377229425f5eb7b2e1e619e" } } ], "extra": [ 1, 12, 244, 138, 251, 226, 209, 55, 100, 118, 174, 117, 244, 165, 133, 109, 230, 182, 242, 189, 109, 143, 71, 40, 70, 40, 126, 9, 63, 112, 158, 255, 154, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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