Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84958deabd5033823ae8c0586d63b9ce9c3e7b3ab9aa3b4c45bec1e10b01d5e4

Tx prefix hash: f3163602f312c094e4f7278c6082e032350a2df3c5362858e83f7b590e105de5
Tx public key: d67896a3ea6de75303b00034b9263ac11bf5084a2b8b05a298f9605a466adc1d
Timestamp: 1725257685 Timestamp [UCT]: 2024-09-02 06:14:45 Age [y:d:h:m:s]: 00:221:02:13:35
Block: 1101144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157872 RingCT/type: yes/0
Extra: 01d67896a3ea6de75303b00034b9263ac11bf5084a2b8b05a298f9605a466adc1d021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 028b50536548fcbc67664ba4381a023ced8cb75c4f57ed2ebe6ac75559e340fb 0.600000000000 1577127 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": 1101154, "vin": [ { "gen": { "height": 1101144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "028b50536548fcbc67664ba4381a023ced8cb75c4f57ed2ebe6ac75559e340fb" } } ], "extra": [ 1, 214, 120, 150, 163, 234, 109, 231, 83, 3, 176, 0, 52, 185, 38, 58, 193, 27, 245, 8, 74, 43, 139, 5, 162, 152, 249, 96, 90, 70, 106, 220, 29, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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