Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c79d7b7cb003c3466b881de652dea94452d796025c1f18d8aaed2721b1a2c648

Tx prefix hash: f01d4c3d68357c538245f091767192511518993f530ad3e358c9f32c4f068b87
Tx public key: 1927d2cc91fcf52e9d9a41335561b3d067bf6b3f3c60d9b494495edfeb52a192
Timestamp: 1730741410 Timestamp [UCT]: 2024-11-04 17:30:10 Age [y:d:h:m:s]: 00:223:20:38:39
Block: 1146519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159762 RingCT/type: yes/0
Extra: 011927d2cc91fcf52e9d9a41335561b3d067bf6b3f3c60d9b494495edfeb52a1920211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 677a9ffe256009bd846a58c9ab1cccebaf01d46e0278ce0d61009d4c0bd42c87 0.600000000000 1631176 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": 1146529, "vin": [ { "gen": { "height": 1146519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "677a9ffe256009bd846a58c9ab1cccebaf01d46e0278ce0d61009d4c0bd42c87" } } ], "extra": [ 1, 25, 39, 210, 204, 145, 252, 245, 46, 157, 154, 65, 51, 85, 97, 179, 208, 103, 191, 107, 63, 60, 96, 217, 180, 148, 73, 94, 223, 235, 82, 161, 146, 2, 17, 0, 0, 0, 1, 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