Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45872e901be059e877761b95b367ed6f7ae120dc15e744be681b1ed93a33643d

Tx prefix hash: 3b5d8e6c39b78a9881e03f9cb36e83b14af6b5b213172b08c7605445196708db
Tx public key: b96a33d0392502670912e8849280757166ec1f7dbcdc7f86f3f045c89403d9f7
Timestamp: 1751530786 Timestamp [UCT]: 2025-07-03 08:19:46 Age [y:d:h:m:s]: 00:141:05:49:24
Block: 1317809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99186 RingCT/type: yes/0
Extra: 01b96a33d0392502670912e8849280757166ec1f7dbcdc7f86f3f045c89403d9f70211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34aeefc4f7f48030eec65e5a0bab32ff1f0b8870a21e8ef7fb6186fb27611da3 0.600000000000 1805480 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": 1317819, "vin": [ { "gen": { "height": 1317809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34aeefc4f7f48030eec65e5a0bab32ff1f0b8870a21e8ef7fb6186fb27611da3" } } ], "extra": [ 1, 185, 106, 51, 208, 57, 37, 2, 103, 9, 18, 232, 132, 146, 128, 117, 113, 102, 236, 31, 125, 188, 220, 127, 134, 243, 240, 69, 200, 148, 3, 217, 247, 2, 17, 0, 0, 0, 1, 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