Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c33dbb9165f23d4e9b4c9c3bfec9fa7860dc12fd5cd67760b3b0a9133aa1c023

Tx prefix hash: da39c72ff4372838641cfc3b41284847e2b092e1620cc481afb42323c7e29dde
Tx public key: b9059e77e318f8db17b6051a3968933d15ac0991eb6fe78adfb7f27c06fce533
Timestamp: 1745758585 Timestamp [UCT]: 2025-04-27 12:56:25 Age [y:d:h:m:s]: 00:243:08:59:34
Block: 1270597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171706 RingCT/type: yes/0
Extra: 01b9059e77e318f8db17b6051a3968933d15ac0991eb6fe78adfb7f27c06fce5330211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c453e1785679e70b50fd14620e0dd7a6a8524a3aa62f278cf5a79cdcc42349d1 0.600000000000 1757840 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": 1270607, "vin": [ { "gen": { "height": 1270597 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c453e1785679e70b50fd14620e0dd7a6a8524a3aa62f278cf5a79cdcc42349d1" } } ], "extra": [ 1, 185, 5, 158, 119, 227, 24, 248, 219, 23, 182, 5, 26, 57, 104, 147, 61, 21, 172, 9, 145, 235, 111, 231, 138, 223, 183, 242, 124, 6, 252, 229, 51, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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