Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dea9fe426704df7460381889fbf85f2ca0d64e84f45af8cc1dcde3aae39c609c

Tx prefix hash: a5cd6b564c79203a8a992eb55ac6b640365cee13eb8adc8cde3921ae429c4d8e
Tx public key: f004832aa7b67d087ba03d051712bf691309c3fc84fa65766d370add80e993de
Timestamp: 1699230816 Timestamp [UCT]: 2023-11-06 00:33:36 Age [y:d:h:m:s]: 01:112:06:00:55
Block: 885358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341389 RingCT/type: yes/0
Extra: 01f004832aa7b67d087ba03d051712bf691309c3fc84fa65766d370add80e993de021100000002faf35c9c000000000000000000

1 output(s) for total of 0.715222916000 dcy

stealth address amount amount idx
00: a057dfefc37052c837283182946c2dfcd6954009f068ff4d5eb8486f47b913c6 0.715222916000 1341125 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": 885368, "vin": [ { "gen": { "height": 885358 } } ], "vout": [ { "amount": 715222916, "target": { "key": "a057dfefc37052c837283182946c2dfcd6954009f068ff4d5eb8486f47b913c6" } } ], "extra": [ 1, 240, 4, 131, 42, 167, 182, 125, 8, 123, 160, 61, 5, 23, 18, 191, 105, 19, 9, 195, 252, 132, 250, 101, 118, 109, 55, 10, 221, 128, 233, 147, 222, 2, 17, 0, 0, 0, 2, 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