Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 075d121dbe05c99a766cfac49a637a4ea472fa131598f4c9c126f2a519462d24

Tx prefix hash: d7bc050a6ea91503ec14aac10c364d9d0decc74a1ede2275715316780688d0de
Tx public key: dea81c22a05365ba03a23e9a90d807febc21fc95ced23e9bd9ea3b2655dc71c2
Timestamp: 1673497969 Timestamp [UCT]: 2023-01-12 04:32:49 Age [y:d:h:m:s]: 02:121:15:44:36
Block: 672885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 608650 RingCT/type: yes/0
Extra: 01dea81c22a05365ba03a23e9a90d807febc21fc95ced23e9bd9ea3b2655dc71c20211000000018b7b6602000000000000000000

1 output(s) for total of 3.617867191000 dcy

stealth address amount amount idx
00: c5d4afa2f23f499d2561d95998af8db5662f3879aa910b0d09f6cf2524816c7e 3.617867191000 1114454 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": 672895, "vin": [ { "gen": { "height": 672885 } } ], "vout": [ { "amount": 3617867191, "target": { "key": "c5d4afa2f23f499d2561d95998af8db5662f3879aa910b0d09f6cf2524816c7e" } } ], "extra": [ 1, 222, 168, 28, 34, 160, 83, 101, 186, 3, 162, 62, 154, 144, 216, 7, 254, 188, 33, 252, 149, 206, 210, 62, 155, 217, 234, 59, 38, 85, 220, 113, 194, 2, 17, 0, 0, 0, 1, 139, 123, 102, 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