Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd0fca3ce7808024ebca13c6bd778d4dc0db113b0882954e6000199a27763793

Tx prefix hash: e964863b18bafbc41755e1ac5ff666a77b476b9f5a1438336ce849ca5439119f
Tx public key: d323a1d79160f24f696cec0a1d199c2cff85b68479cd9a24c2dd92a8409d8579
Timestamp: 1692854140 Timestamp [UCT]: 2023-08-24 05:15:40 Age [y:d:h:m:s]: 01:205:23:47:15
Block: 832674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408369 RingCT/type: yes/0
Extra: 01d323a1d79160f24f696cec0a1d199c2cff85b68479cd9a24c2dd92a8409d857902110000000275e3f0e9000000000000000000

1 output(s) for total of 1.069068321000 dcy

stealth address amount amount idx
00: 2fab736531125e95b0f0ea470e2569bef4999de1e7f47f0a984f29e8be367b2e 1.069068321000 1285124 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": 832684, "vin": [ { "gen": { "height": 832674 } } ], "vout": [ { "amount": 1069068321, "target": { "key": "2fab736531125e95b0f0ea470e2569bef4999de1e7f47f0a984f29e8be367b2e" } } ], "extra": [ 1, 211, 35, 161, 215, 145, 96, 242, 79, 105, 108, 236, 10, 29, 25, 156, 44, 255, 133, 182, 132, 121, 205, 154, 36, 194, 221, 146, 168, 64, 157, 133, 121, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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