Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87a300b24b4c5b6468f97184eb1827e951d66cc2beef238b1d775e03df53339f

Tx prefix hash: bfac8bde80699445824e5348d3ab3a36941f074136e4e2d0c108bb3fb5fff0bc
Tx public key: 4287396d7ff69ae5165e6ca9ff35f841cdf4a83d46e83977b579104c02d23d45
Timestamp: 1711964762 Timestamp [UCT]: 2024-04-01 09:46:02 Age [y:d:h:m:s]: 01:057:17:59:10
Block: 990905 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302313 RingCT/type: yes/0
Extra: 014287396d7ff69ae5165e6ca9ff35f841cdf4a83d46e83977b579104c02d23d450211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3298f86095b0744c170f958313b0d26cfedaaa67de1dbf746ea35a7d8630be1b 0.600000000000 1451237 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": 990915, "vin": [ { "gen": { "height": 990905 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3298f86095b0744c170f958313b0d26cfedaaa67de1dbf746ea35a7d8630be1b" } } ], "extra": [ 1, 66, 135, 57, 109, 127, 246, 154, 229, 22, 94, 108, 169, 255, 53, 248, 65, 205, 244, 168, 61, 70, 232, 57, 119, 181, 121, 16, 76, 2, 210, 61, 69, 2, 17, 0, 0, 0, 2, 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