Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4351ebbca52237c276257954da05db8c0840e4e0a30c150a83bcd2174c9c8a18

Tx prefix hash: 873f4e843a07947cf477ca2b94bdbfcea9b7f4f5a8796abf5a9e0637cdd1d02c
Tx public key: 879862d8d6faa30a8bee07a50a894894fb33d8ccd4b3627833473bbb1b1b006a
Timestamp: 1751503186 Timestamp [UCT]: 2025-07-03 00:39:46 Age [y:d:h:m:s]: 00:189:10:19:19
Block: 1317585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133701 RingCT/type: yes/0
Extra: 01879862d8d6faa30a8bee07a50a894894fb33d8ccd4b3627833473bbb1b1b006a02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ce5ec4817587b0f411c870a5f83340b1bb1da9f81e99056758ff7b5a0df85c7 0.600000000000 1805254 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": 1317595, "vin": [ { "gen": { "height": 1317585 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ce5ec4817587b0f411c870a5f83340b1bb1da9f81e99056758ff7b5a0df85c7" } } ], "extra": [ 1, 135, 152, 98, 216, 214, 250, 163, 10, 139, 238, 7, 165, 10, 137, 72, 148, 251, 51, 216, 204, 212, 179, 98, 120, 51, 71, 59, 187, 27, 27, 0, 106, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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