Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d8aaddda7fe3489b76a8f0435a953d3d09801f1be26957345ae42338a949b2e

Tx prefix hash: af8bfb9a2d131bf6613f53bf8efd9a17b92f8018e956a79ed5dfbfbce06408f9
Tx public key: 5d0d19e42dc8d4838b4749d723c63df31d3cc618e215cde6107dedadd5243800
Timestamp: 1731965543 Timestamp [UCT]: 2024-11-18 21:32:23 Age [y:d:h:m:s]: 00:124:11:01:20
Block: 1156653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88777 RingCT/type: yes/0
Extra: 015d0d19e42dc8d4838b4749d723c63df31d3cc618e215cde6107dedadd5243800021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80c18596e228be9ee99198c2d063f10b307158f1ad042550a8428f4c21f108f0 0.600000000000 1642276 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": 1156663, "vin": [ { "gen": { "height": 1156653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80c18596e228be9ee99198c2d063f10b307158f1ad042550a8428f4c21f108f0" } } ], "extra": [ 1, 93, 13, 25, 228, 45, 200, 212, 131, 139, 71, 73, 215, 35, 198, 61, 243, 29, 60, 198, 24, 226, 21, 205, 230, 16, 125, 237, 173, 213, 36, 56, 0, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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