Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e11f006e3f1da0357b90433b7095f4f2384aa90f6ae6e655cdcb4b78be57f5d3

Tx prefix hash: 9866ad039ce3eb0433b03a407feea92f2b51f03074cfa87a82c883f41d12aa8e
Tx public key: 68074105046964ebd7e5e5c4b022e9f1e3d709251cf124e366dc393e96991047
Timestamp: 1739221877 Timestamp [UCT]: 2025-02-10 21:11:17 Age [y:d:h:m:s]: 00:332:08:41:35
Block: 1216479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235368 RingCT/type: yes/0
Extra: 0168074105046964ebd7e5e5c4b022e9f1e3d709251cf124e366dc393e969910470211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc18c55ab019285727fb9f8a0d35d682192f6f89041fb963ae19385c9967ca02 0.600000000000 1703284 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": 1216489, "vin": [ { "gen": { "height": 1216479 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc18c55ab019285727fb9f8a0d35d682192f6f89041fb963ae19385c9967ca02" } } ], "extra": [ 1, 104, 7, 65, 5, 4, 105, 100, 235, 215, 229, 229, 196, 176, 34, 233, 241, 227, 215, 9, 37, 28, 241, 36, 227, 102, 220, 57, 62, 150, 153, 16, 71, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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