Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 034cfaf189967e1475bbdc5c566250a1ece0cfd23fb8ffbcc101776ebec5baf2

Tx prefix hash: d0fd63a290e4a0fad19242df7f6982ee5251b9c876ae7a212d3d097b9a0501d7
Tx public key: 4d189091689d851fa69addbd7c7b92f91bd6b6e8a2147d057a23bb8fe56ada92
Timestamp: 1577726027 Timestamp [UCT]: 2019-12-30 17:13:47 Age [y:d:h:m:s]: 05:306:07:06:53
Block: 35174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1366396 RingCT/type: yes/0
Extra: 014d189091689d851fa69addbd7c7b92f91bd6b6e8a2147d057a23bb8fe56ada920211000000024ac5aa02000000000000000000

1 output(s) for total of 469.352428613000 dcy

stealth address amount amount idx
00: 89f44501f175b32ea48456a45e54444e3dadfa4c7305b021ca9c22f031e9df4e 469.352428613000 59246 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": 35184, "vin": [ { "gen": { "height": 35174 } } ], "vout": [ { "amount": 469352428613, "target": { "key": "89f44501f175b32ea48456a45e54444e3dadfa4c7305b021ca9c22f031e9df4e" } } ], "extra": [ 1, 77, 24, 144, 145, 104, 157, 133, 31, 166, 154, 221, 189, 124, 123, 146, 249, 27, 214, 182, 232, 162, 20, 125, 5, 122, 35, 187, 143, 229, 106, 218, 146, 2, 17, 0, 0, 0, 2, 74, 197, 170, 2, 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