Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 183d2bc8f4de04333c05837c33abf0f13445d5e50f9663bec47fab2c5c9c37b3

Tx prefix hash: c0e6a5b5db8baddb76f26e0cea0c5536eca9fb274443a9c1c99e53c0ca2441f1
Tx public key: 019e96b1c2404477eb65fd4c453868ff6cb8f8dfa4ea3b7bea4afc5c71c9e444
Timestamp: 1724869012 Timestamp [UCT]: 2024-08-28 18:16:52 Age [y:d:h:m:s]: 00:229:12:20:57
Block: 1097915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163898 RingCT/type: yes/0
Extra: 01019e96b1c2404477eb65fd4c453868ff6cb8f8dfa4ea3b7bea4afc5c71c9e444021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 083d2c2260d7a55bc535635a812798fcf00f74c995b55c7717f94c572e02896e 0.600000000000 1573452 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": 1097925, "vin": [ { "gen": { "height": 1097915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "083d2c2260d7a55bc535635a812798fcf00f74c995b55c7717f94c572e02896e" } } ], "extra": [ 1, 1, 158, 150, 177, 194, 64, 68, 119, 235, 101, 253, 76, 69, 56, 104, 255, 108, 184, 248, 223, 164, 234, 59, 123, 234, 74, 252, 92, 113, 201, 228, 68, 2, 17, 0, 0, 0, 3, 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