Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6e8858beac5882212f5740d76bb221fb098a0fbcbc14b8388f986e3943f1689

Tx prefix hash: e99ed084c5aeb7715a2b4a504b06fce22f3db7bb47bb72286a87dc321fd62f7e
Tx public key: 86277e6efa2ff2d1d53141da5cab2abfbb403eb8ce8770a7574a564a120f7891
Timestamp: 1721420284 Timestamp [UCT]: 2024-07-19 20:18:04 Age [y:d:h:m:s]: 00:299:07:21:23
Block: 1069367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213817 RingCT/type: yes/0
Extra: 0186277e6efa2ff2d1d53141da5cab2abfbb403eb8ce8770a7574a564a120f78910211000000020bba16d7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b75dd7c1e0074b313dba961148bd0ce69f4f97de61535af46c7c2e1d1b112ca 0.600000000000 1540756 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": 1069377, "vin": [ { "gen": { "height": 1069367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b75dd7c1e0074b313dba961148bd0ce69f4f97de61535af46c7c2e1d1b112ca" } } ], "extra": [ 1, 134, 39, 126, 110, 250, 47, 242, 209, 213, 49, 65, 218, 92, 171, 42, 191, 187, 64, 62, 184, 206, 135, 112, 167, 87, 74, 86, 74, 18, 15, 120, 145, 2, 17, 0, 0, 0, 2, 11, 186, 22, 215, 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