Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72d916f158d8102d2c001449139d975e38ac852403a49ea8b0ee5f840f6a09da

Tx prefix hash: f498a6edd5e85dcf55a33acb96fe9a9d8e7aeeb23e7511ef2f4cb890651b41e5
Tx public key: f97fb5a4e3a3ed895f378e2509fa0613c7600ec6a0720b085ec63b39707e9e28
Timestamp: 1757380264 Timestamp [UCT]: 2025-09-09 01:11:04 Age [y:d:h:m:s]: 00:064:06:23:04
Block: 1364422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45938 RingCT/type: yes/0
Extra: 01f97fb5a4e3a3ed895f378e2509fa0613c7600ec6a0720b085ec63b39707e9e28021100000007ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: da5ba334eb8ffdc79aed23ff5ec1cbf581bb10c573a88bdc24699be0ea6a653c 0.600000000000 1852461 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": 1364432, "vin": [ { "gen": { "height": 1364422 } } ], "vout": [ { "amount": 600000000, "target": { "key": "da5ba334eb8ffdc79aed23ff5ec1cbf581bb10c573a88bdc24699be0ea6a653c" } } ], "extra": [ 1, 249, 127, 181, 164, 227, 163, 237, 137, 95, 55, 142, 37, 9, 250, 6, 19, 199, 96, 14, 198, 160, 114, 11, 8, 94, 198, 59, 57, 112, 126, 158, 40, 2, 17, 0, 0, 0, 7, 173, 121, 72, 208, 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