Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7975f24f3d8ef338f551688fb9105a3865549f18c5c65b808d0a3cfe0d82b9d

Tx prefix hash: b90800d2c2d9de1bcb7a048ab61f8fbbd362d892384bfdd939f0d655254e4d57
Tx public key: 317a65760aea2d37a05770bd0674aecb8de1f8d0186a791a49afbd3b3dd398ae
Timestamp: 1695458850 Timestamp [UCT]: 2023-09-23 08:47:30 Age [y:d:h:m:s]: 01:116:08:17:28
Block: 854290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344447 RingCT/type: yes/0
Extra: 01317a65760aea2d37a05770bd0674aecb8de1f8d0186a791a49afbd3b3dd398ae0211000000054b8f5122000000000000000000

1 output(s) for total of 0.906530974000 dcy

stealth address amount amount idx
00: 67029c6ccc91e211fb66d8d12d14d3feed85ea436e73b5199bcbc7c641b95785 0.906530974000 1308256 of 0

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": 854300, "vin": [ { "gen": { "height": 854290 } } ], "vout": [ { "amount": 906530974, "target": { "key": "67029c6ccc91e211fb66d8d12d14d3feed85ea436e73b5199bcbc7c641b95785" } } ], "extra": [ 1, 49, 122, 101, 118, 10, 234, 45, 55, 160, 87, 112, 189, 6, 116, 174, 203, 141, 225, 248, 208, 24, 106, 121, 26, 73, 175, 189, 59, 61, 211, 152, 174, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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