Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9932cb91d27229b71c9babb714588099b1fb1b51657ff5b783fee89af74fe0e

Tx prefix hash: 9de98bef177de8878721b10e9c5fd2dffa4c92d04eb9cd2d43897405b0d029b3
Tx public key: 8bd2c552a80e942851d2d2dc72a7ed20aeac1254ad30d2654bdc3deb11162834
Timestamp: 1750935734 Timestamp [UCT]: 2025-06-26 11:02:14 Age [y:d:h:m:s]: 00:146:21:16:49
Block: 1313136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102978 RingCT/type: yes/0
Extra: 018bd2c552a80e942851d2d2dc72a7ed20aeac1254ad30d2654bdc3deb111628340211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b06664084c25c1cb2a61aa2e94ec3b909369303f87d6a5603c48d8c64d8a1106 0.600000000000 1800775 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": 1313146, "vin": [ { "gen": { "height": 1313136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b06664084c25c1cb2a61aa2e94ec3b909369303f87d6a5603c48d8c64d8a1106" } } ], "extra": [ 1, 139, 210, 197, 82, 168, 14, 148, 40, 81, 210, 210, 220, 114, 167, 237, 32, 174, 172, 18, 84, 173, 48, 210, 101, 75, 220, 61, 235, 17, 22, 40, 52, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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