Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1339e4a3efc18071f7e6ffa2b4ba4b3f1d213658f88506d9a87324811a612df

Tx prefix hash: 7b51e2b0ff6997b07b37dfdc6148dd9bc43048832c678759a9a3538c28d720e8
Tx public key: 75f3d59e45f104ac68b84dd83ee1c962bf743b5963808065fd4db91715ac07db
Timestamp: 1696116429 Timestamp [UCT]: 2023-09-30 23:27:09 Age [y:d:h:m:s]: 01:188:13:50:13
Block: 859754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395811 RingCT/type: yes/0
Extra: 0175f3d59e45f104ac68b84dd83ee1c962bf743b5963808065fd4db91715ac07db0211000000094b8f5122000000000000000000

1 output(s) for total of 0.869517124000 dcy

stealth address amount amount idx
00: 17297bda296094d52c19c98534b38578adac2ca8e07b1953a2d29a39fca6587f 0.869517124000 1313998 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": 859764, "vin": [ { "gen": { "height": 859754 } } ], "vout": [ { "amount": 869517124, "target": { "key": "17297bda296094d52c19c98534b38578adac2ca8e07b1953a2d29a39fca6587f" } } ], "extra": [ 1, 117, 243, 213, 158, 69, 241, 4, 172, 104, 184, 77, 216, 62, 225, 201, 98, 191, 116, 59, 89, 99, 128, 128, 101, 253, 77, 185, 23, 21, 172, 7, 219, 2, 17, 0, 0, 0, 9, 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