Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02b308d30d03a6bc2ae1ec181149f38ddd57e9ff913c9a9a8c0ba06a8ec53588

Tx prefix hash: 3ba938545ab412e11327ebb61da6a4b976caa960fc36ed20bc6b05c3edcc7d17
Tx public key: eca0fa8f5f4df02942de68a84ff986e24b323509dc381c31225c9c29c2de8e60
Timestamp: 1759246522 Timestamp [UCT]: 2025-09-30 15:35:22 Age [y:d:h:m:s]: 00:124:06:22:03
Block: 1379809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88807 RingCT/type: yes/0
Extra: 01eca0fa8f5f4df02942de68a84ff986e24b323509dc381c31225c9c29c2de8e60021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2ae637052475c149275908f8924a07e882ca771e9690cd9a7763375ffcbd313a 0.600000000000 1867918 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": 1379819, "vin": [ { "gen": { "height": 1379809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2ae637052475c149275908f8924a07e882ca771e9690cd9a7763375ffcbd313a" } } ], "extra": [ 1, 236, 160, 250, 143, 95, 77, 240, 41, 66, 222, 104, 168, 79, 249, 134, 226, 75, 50, 53, 9, 220, 56, 28, 49, 34, 92, 156, 41, 194, 222, 142, 96, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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