Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da7f0a2a234f1815b04bb05a913fa40ee8bc9ed513ad3221d1c2934a0faef277

Tx prefix hash: fcdb2a3a6b2da7bb17d0b3784e23612b1997ea9805193b9d676a1d73914487a1
Tx public key: faebdcf1b18fd4db17f306867a4d5edf238f2b6ec9675ca7d7f5d1752c4a38b2
Timestamp: 1725290633 Timestamp [UCT]: 2024-09-02 15:23:53 Age [y:d:h:m:s]: 01:036:16:56:00
Block: 1101417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284625 RingCT/type: yes/0
Extra: 01faebdcf1b18fd4db17f306867a4d5edf238f2b6ec9675ca7d7f5d1752c4a38b2021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0716a8a4923073722154d2785a364124e69f1d8f3bcaf6dcbeb861906f69dd23 0.600000000000 1577458 of 15

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": 1101427, "vin": [ { "gen": { "height": 1101417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0716a8a4923073722154d2785a364124e69f1d8f3bcaf6dcbeb861906f69dd23" } } ], "extra": [ 1, 250, 235, 220, 241, 177, 143, 212, 219, 23, 243, 6, 134, 122, 77, 94, 223, 35, 143, 43, 110, 201, 103, 92, 167, 215, 245, 209, 117, 44, 74, 56, 178, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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