Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58c456fe9b2efff6befd2320b89aa642cffce7449592cccfe193ccbeecd52498

Tx prefix hash: 4627293aba7cf685e1c32ee8765a32faa425355185c265b45da35e6892d2c8d7
Tx public key: fce4bb1c9de186d8e6b6cb3a4f96a9646e804802124d3727d16c4b2cd923a555
Timestamp: 1710181244 Timestamp [UCT]: 2024-03-11 18:20:44 Age [y:d:h:m:s]: 01:266:00:16:28
Block: 976163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 448853 RingCT/type: yes/0
Extra: 01fce4bb1c9de186d8e6b6cb3a4f96a9646e804802124d3727d16c4b2cd923a5550211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 932ff4c5bc10bed3fcbaac951498a5a3491c3d1528c11a60be261811275426ff 0.600000000000 1436154 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": 976173, "vin": [ { "gen": { "height": 976163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "932ff4c5bc10bed3fcbaac951498a5a3491c3d1528c11a60be261811275426ff" } } ], "extra": [ 1, 252, 228, 187, 28, 157, 225, 134, 216, 230, 182, 203, 58, 79, 150, 169, 100, 110, 128, 72, 2, 18, 77, 55, 39, 209, 108, 75, 44, 217, 35, 165, 85, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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