Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6bb8ac437b505739c83462a4bd00ad2201d8cf649b724592af44d3ae50f1c2a7

Tx prefix hash: 0b744fe60dfd422be5c836eaedd6a75586f2128ebb9d1798714c248db9d12cff
Tx public key: ad6d8c3cf2c4d70d7dc6494adcc52564e8c9e5ce3494210d02552dd220257e52
Timestamp: 1754095236 Timestamp [UCT]: 2025-08-02 00:40:36 Age [y:d:h:m:s]: 00:079:04:56:15
Block: 1338390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55468 RingCT/type: yes/0
Extra: 01ad6d8c3cf2c4d70d7dc6494adcc52564e8c9e5ce3494210d02552dd220257e52021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d13298af75a9d6de7e1f3f9a60266f307cd364dbe6c25a560a915c7cd70b99e 0.600000000000 1826197 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": 1338400, "vin": [ { "gen": { "height": 1338390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d13298af75a9d6de7e1f3f9a60266f307cd364dbe6c25a560a915c7cd70b99e" } } ], "extra": [ 1, 173, 109, 140, 60, 242, 196, 215, 13, 125, 198, 73, 74, 220, 197, 37, 100, 232, 201, 229, 206, 52, 148, 33, 13, 2, 85, 45, 210, 32, 37, 126, 82, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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