Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2842d3863ceb088ad968857039f8476f667c9c0ef0437ac892f6a931107e42e6

Tx prefix hash: 38c21b1b744815a5a402ec41c4637e35dc203021a88391b1612822f4b4de39ec
Tx public key: 697c39fa538656b91341f11a7fbb816d7669d22d7ec78b5e2b2c34c084031c47
Timestamp: 1750696281 Timestamp [UCT]: 2025-06-23 16:31:21 Age [y:d:h:m:s]: 00:149:15:30:08
Block: 1311246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104859 RingCT/type: yes/0
Extra: 01697c39fa538656b91341f11a7fbb816d7669d22d7ec78b5e2b2c34c084031c4702110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d572648110d6b1fcc2a0087cffd9b836d0f4335d6f2918a8d205e4043ccb73f6 0.600000000000 1798871 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": 1311256, "vin": [ { "gen": { "height": 1311246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d572648110d6b1fcc2a0087cffd9b836d0f4335d6f2918a8d205e4043ccb73f6" } } ], "extra": [ 1, 105, 124, 57, 250, 83, 134, 86, 185, 19, 65, 241, 26, 127, 187, 129, 109, 118, 105, 210, 45, 126, 199, 139, 94, 43, 44, 52, 192, 132, 3, 28, 71, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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