Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53d0057e26d563490461fc377e28dc814623a601eddef38f481c9a3ae0ee06e2

Tx prefix hash: 8d7db329285967560e021c32c13f5787a4f2367cc4cbd8e1cf67601a49d9866d
Tx public key: b2f18d08aa84fe3366a6f481e558cc6ef99ea0c6a9df79a98d78e76d894bfd00
Timestamp: 1762381479 Timestamp [UCT]: 2025-11-05 22:24:39 Age [y:d:h:m:s]: 00:047:23:57:32
Block: 1405776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34379 RingCT/type: yes/0
Extra: 01b2f18d08aa84fe3366a6f481e558cc6ef99ea0c6a9df79a98d78e76d894bfd0002110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c6ae952bfb2d749859cf4d5d33ff2f20b04be93a87c870692c6687c30db8379 0.600000000000 1894157 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": 1405786, "vin": [ { "gen": { "height": 1405776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c6ae952bfb2d749859cf4d5d33ff2f20b04be93a87c870692c6687c30db8379" } } ], "extra": [ 1, 178, 241, 141, 8, 170, 132, 254, 51, 102, 166, 244, 129, 229, 88, 204, 110, 249, 158, 160, 198, 169, 223, 121, 169, 141, 120, 231, 109, 137, 75, 253, 0, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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