Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abd07c6c02404b76afc439b2e56df3e56d260d60eb89988477e63d5340127c0d

Tx prefix hash: be962cd2b2161d9acbbb57f092c62e77d34181b93d6b5fa6473489cd0cfe9f18
Tx public key: 37d75fa0e94f8f24eb31128663d9d3d1f03a9abdcbdfa0c154b121716189a783
Timestamp: 1754915109 Timestamp [UCT]: 2025-08-11 12:25:09 Age [y:d:h:m:s]: 00:102:05:25:27
Block: 1344816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72289 RingCT/type: yes/0
Extra: 0137d75fa0e94f8f24eb31128663d9d3d1f03a9abdcbdfa0c154b121716189a7830211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d5ed7a8b2820097bef5c875d7a66ac1358fa4a5c99e131c4e35498e27e18782 0.600000000000 1832701 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": 1344826, "vin": [ { "gen": { "height": 1344816 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d5ed7a8b2820097bef5c875d7a66ac1358fa4a5c99e131c4e35498e27e18782" } } ], "extra": [ 1, 55, 215, 95, 160, 233, 79, 143, 36, 235, 49, 18, 134, 99, 217, 211, 209, 240, 58, 154, 189, 203, 223, 160, 193, 84, 177, 33, 113, 97, 137, 167, 131, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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