Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d35d5225b4e0b63094a143e8298c838a5ae55afd24b99cd2397d5ffa63bf9a49

Tx prefix hash: 3113eb45564e68729bff485e872b3b449a64391a9d46508101e7f264d57d24fc
Tx public key: 6013f7eea6d001657c489ce556a2b7be2bc8e8e9c3c57ea944f055856587a13e
Timestamp: 1700659935 Timestamp [UCT]: 2023-11-22 13:32:15 Age [y:d:h:m:s]: 01:139:19:40:02
Block: 897216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361099 RingCT/type: yes/0
Extra: 016013f7eea6d001657c489ce556a2b7be2bc8e8e9c3c57ea944f055856587a13e021100000001faf35c9c000000000000000000

1 output(s) for total of 0.653357570000 dcy

stealth address amount amount idx
00: 8e697cb77b07b862e5e95577c1ad52c8b314bc179e5897a57be13e2b97bbd123 0.653357570000 1353581 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": 897226, "vin": [ { "gen": { "height": 897216 } } ], "vout": [ { "amount": 653357570, "target": { "key": "8e697cb77b07b862e5e95577c1ad52c8b314bc179e5897a57be13e2b97bbd123" } } ], "extra": [ 1, 96, 19, 247, 238, 166, 208, 1, 101, 124, 72, 156, 229, 86, 162, 183, 190, 43, 200, 232, 233, 195, 197, 126, 169, 68, 240, 85, 133, 101, 135, 161, 62, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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