Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf302c04af93f9afa707f29007ae88d96c34f68a34e14f6cfe0bd1de30b42543

Tx prefix hash: 61b5f3255caf0c6815a7d49a02c46285c40d23d389ef4fe910a5768ae138dd7c
Tx public key: a571c2a6bcd9dfb636710f8f9150e168697d6869acb8a292a859e7a10705806e
Timestamp: 1757666629 Timestamp [UCT]: 2025-09-12 08:43:49 Age [y:d:h:m:s]: 00:060:11:50:48
Block: 1366712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43324 RingCT/type: yes/0
Extra: 01a571c2a6bcd9dfb636710f8f9150e168697d6869acb8a292a859e7a10705806e021100000001b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ceb21ca1777fbaaae4bf34488654ededdf5aa0856a5b26a256c48436e5e8806c 0.600000000000 1854751 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": 1366722, "vin": [ { "gen": { "height": 1366712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ceb21ca1777fbaaae4bf34488654ededdf5aa0856a5b26a256c48436e5e8806c" } } ], "extra": [ 1, 165, 113, 194, 166, 188, 217, 223, 182, 54, 113, 15, 143, 145, 80, 225, 104, 105, 125, 104, 105, 172, 184, 162, 146, 168, 89, 231, 161, 7, 5, 128, 110, 2, 17, 0, 0, 0, 1, 178, 247, 132, 196, 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