Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71d067f7be07adc2e0cd061c1afb601de792f2df1d8ff853b78d45e2a0e1193e

Tx prefix hash: e608eb93aeff9a764b6a1b1566f9a3d16384f63d4412c67f66205ddee639daf9
Tx public key: a21d03d8527f447984734be8aea1e4692ce619bb8675bc6f00de44efb09d8822
Timestamp: 1720706090 Timestamp [UCT]: 2024-07-11 13:54:50 Age [y:d:h:m:s]: 00:286:21:05:26
Block: 1063415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204974 RingCT/type: yes/0
Extra: 01a21d03d8527f447984734be8aea1e4692ce619bb8675bc6f00de44efb09d882202110000000e91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02c5140bd187dff5d8f4dc312e28a3237ee98d6102bfa9e7f35e1a24afdd6408 0.600000000000 1533930 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": 1063425, "vin": [ { "gen": { "height": 1063415 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02c5140bd187dff5d8f4dc312e28a3237ee98d6102bfa9e7f35e1a24afdd6408" } } ], "extra": [ 1, 162, 29, 3, 216, 82, 127, 68, 121, 132, 115, 75, 232, 174, 161, 228, 105, 44, 230, 25, 187, 134, 117, 188, 111, 0, 222, 68, 239, 176, 157, 136, 34, 2, 17, 0, 0, 0, 14, 145, 225, 60, 4, 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