Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec22fe0fb66fda52385e6a52f7eb219d11aefbd64258c0f81580c1e3b7d0e9bb

Tx prefix hash: 9a89dc50b472b4ebe0152747518544b383fff16766e6489d53999d1c7ebbe517
Tx public key: 2843f8cf1c61ca34d241799a91a8fc5e47a954e9bbe6448706f49bb8becf67e6
Timestamp: 1737809199 Timestamp [UCT]: 2025-01-25 12:46:39 Age [y:d:h:m:s]: 00:143:03:13:34
Block: 1205010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102041 RingCT/type: yes/0
Extra: 012843f8cf1c61ca34d241799a91a8fc5e47a954e9bbe6448706f49bb8becf67e6021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4274193e70df3a4bc3e2dc9440f6db279b285bd08204b65c0d2aa223a0c91c63 0.600000000000 1691705 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": 1205020, "vin": [ { "gen": { "height": 1205010 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4274193e70df3a4bc3e2dc9440f6db279b285bd08204b65c0d2aa223a0c91c63" } } ], "extra": [ 1, 40, 67, 248, 207, 28, 97, 202, 52, 210, 65, 121, 154, 145, 168, 252, 94, 71, 169, 84, 233, 187, 230, 68, 135, 6, 244, 155, 184, 190, 207, 103, 230, 2, 17, 0, 0, 0, 7, 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