Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa59cee722c4c36dc7b802b0f8c09fa5d486db5dce7d9085ccdff8a88a22c1cc

Tx prefix hash: 6bbd14e98f8284c99a9dc30cfe4752cc5b942f016d1a3baf920ebd53ff4fd0eb
Tx public key: 47a4dff13a82c9cf8c74462e8d2c6445a2f86ea631f04e164db161f2d46c2bea
Timestamp: 1762949196 Timestamp [UCT]: 2025-11-12 12:06:36 Age [y:d:h:m:s]: 00:046:16:38:51
Block: 1410495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33440 RingCT/type: yes/0
Extra: 0147a4dff13a82c9cf8c74462e8d2c6445a2f86ea631f04e164db161f2d46c2bea021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 327469ddbe261d2f78362d07cd782843110f98c9cfda233ae49ddd40b94a2d1c 0.600000000000 1898946 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": 1410505, "vin": [ { "gen": { "height": 1410495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "327469ddbe261d2f78362d07cd782843110f98c9cfda233ae49ddd40b94a2d1c" } } ], "extra": [ 1, 71, 164, 223, 241, 58, 130, 201, 207, 140, 116, 70, 46, 141, 44, 100, 69, 162, 248, 110, 166, 49, 240, 78, 22, 77, 177, 97, 242, 212, 108, 43, 234, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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