Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2ffb5c9230ae9bac3e45de4c79edff41c64711817f3ad8116b4bfa5006e41fb

Tx prefix hash: df3976d480e6e683de35c3c98c0f48c4fdde67da20c9acce477000521da8d0aa
Tx public key: da0444badb1bc0ad3bd73eff23b2dd94525d06dbcb16afd5fd253d1bd1fe87cd
Timestamp: 1708919217 Timestamp [UCT]: 2024-02-26 03:46:57 Age [y:d:h:m:s]: 01:253:13:03:07
Block: 965697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439917 RingCT/type: yes/0
Extra: 01da0444badb1bc0ad3bd73eff23b2dd94525d06dbcb16afd5fd253d1bd1fe87cd0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b0bda4cfaec243a0862832948d0759307d94032ee4ee677d56620d5335ee7ba 0.600000000000 1425452 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": 965707, "vin": [ { "gen": { "height": 965697 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b0bda4cfaec243a0862832948d0759307d94032ee4ee677d56620d5335ee7ba" } } ], "extra": [ 1, 218, 4, 68, 186, 219, 27, 192, 173, 59, 215, 62, 255, 35, 178, 221, 148, 82, 93, 6, 219, 203, 22, 175, 213, 253, 37, 61, 27, 209, 254, 135, 205, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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