Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48646f221f80a81d0683f49be5efe6824ca3cc48c035fd50d1b94c03ce38ead6

Tx prefix hash: abe35489429b69b7eb9a4932a0b7019d08a86df39be4d71b6ff611f2cf228571
Tx public key: d3bf30835f25a54ab0bf3f48aa200b593c9f94fc75e5f11490c2a2ddaae6702a
Timestamp: 1718512753 Timestamp [UCT]: 2024-06-16 04:39:13 Age [y:d:h:m:s]: 00:272:01:23:41
Block: 1045240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194401 RingCT/type: yes/0
Extra: 01d3bf30835f25a54ab0bf3f48aa200b593c9f94fc75e5f11490c2a2ddaae6702a021100000001f0f115fa000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 236a994693faa94958c64e98087662dfdbf2e910e0abd42003972e6e916c10b0 0.600000000000 1514757 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": 1045250, "vin": [ { "gen": { "height": 1045240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "236a994693faa94958c64e98087662dfdbf2e910e0abd42003972e6e916c10b0" } } ], "extra": [ 1, 211, 191, 48, 131, 95, 37, 165, 74, 176, 191, 63, 72, 170, 32, 11, 89, 60, 159, 148, 252, 117, 229, 241, 20, 144, 194, 162, 221, 170, 230, 112, 42, 2, 17, 0, 0, 0, 1, 240, 241, 21, 250, 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