Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e0d9d1472ccb3fb2cf8c708357cd055a7645c815dbdf5e9826dc89eb4b006ab

Tx prefix hash: 94a160d10b9da1d96ca39313e4185d215caa03257ea9594b751cf0a785946d01
Tx public key: 8326225bee48a24f520fbb0b8f0c8377b336c99262676a0f35b3cf702fb9466b
Timestamp: 1725593322 Timestamp [UCT]: 2024-09-06 03:28:42 Age [y:d:h:m:s]: 00:069:23:39:04
Block: 1103925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50033 RingCT/type: yes/0
Extra: 018326225bee48a24f520fbb0b8f0c8377b336c99262676a0f35b3cf702fb9466b021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2f1ea576d30a1f7ba41cca6b79b910ed88424362dd66022d25367583b783bec 0.600000000000 1580944 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": 1103935, "vin": [ { "gen": { "height": 1103925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2f1ea576d30a1f7ba41cca6b79b910ed88424362dd66022d25367583b783bec" } } ], "extra": [ 1, 131, 38, 34, 91, 238, 72, 162, 79, 82, 15, 187, 11, 143, 12, 131, 119, 179, 54, 201, 146, 98, 103, 106, 15, 53, 179, 207, 112, 47, 185, 70, 107, 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