Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e22b68bbb783f395a70bcb8d37cb97edc54b45bc4bcf57e656114d496411abc

Tx prefix hash: d7cfc3487820571e5edd936b77d83764346a21767340222986b8a0c2e9dce9a2
Tx public key: 4aaa1757443d287bc2bea6106d1ccb48e70cf457d455d24598b7d69d4ac2777a
Timestamp: 1583857048 Timestamp [UCT]: 2020-03-10 16:17:28 Age [y:d:h:m:s]: 04:117:20:38:05
Block: 79965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 979112 RingCT/type: yes/0
Extra: 014aaa1757443d287bc2bea6106d1ccb48e70cf457d455d24598b7d69d4ac2777a02110000000478e4872e000000000000000000

1 output(s) for total of 333.459849593000 dcy

stealth address amount amount idx
00: 0a7f7c8eae4809fc2d07dba94d42c64558e8301a57e47c456757b7a9194cbfcd 333.459849593000 146307 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": 79975, "vin": [ { "gen": { "height": 79965 } } ], "vout": [ { "amount": 333459849593, "target": { "key": "0a7f7c8eae4809fc2d07dba94d42c64558e8301a57e47c456757b7a9194cbfcd" } } ], "extra": [ 1, 74, 170, 23, 87, 68, 61, 40, 123, 194, 190, 166, 16, 109, 28, 203, 72, 231, 12, 244, 87, 212, 85, 210, 69, 152, 183, 214, 157, 74, 194, 119, 122, 2, 17, 0, 0, 0, 4, 120, 228, 135, 46, 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