Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9c1a650f140451701f4eb3ae2ddf8a957917fd6aabb876e50bc6e551836fe8a

Tx prefix hash: 19edb248b707b4f503fce57767f24811054848df6a545f2ebf709237b327b9c9
Tx public key: d3b5e66ecc879b95db4199e770b62c291e12f02324120a3befa1682f9f35c1b1
Timestamp: 1748236456 Timestamp [UCT]: 2025-05-26 05:14:16 Age [y:d:h:m:s]: 00:177:08:54:17
Block: 1291116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124454 RingCT/type: yes/0
Extra: 01d3b5e66ecc879b95db4199e770b62c291e12f02324120a3befa1682f9f35c1b10211000000041f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aab040c2ce351e392eb06201601864bd1b6f2e12ea8909ac6c9cd8f567b9e4b4 0.600000000000 1778587 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": 1291126, "vin": [ { "gen": { "height": 1291116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aab040c2ce351e392eb06201601864bd1b6f2e12ea8909ac6c9cd8f567b9e4b4" } } ], "extra": [ 1, 211, 181, 230, 110, 204, 135, 155, 149, 219, 65, 153, 231, 112, 182, 44, 41, 30, 18, 240, 35, 36, 18, 10, 59, 239, 161, 104, 47, 159, 53, 193, 177, 2, 17, 0, 0, 0, 4, 31, 144, 81, 122, 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